Quantcast
Channel: Service Bus forum
Viewing all articles
Browse latest Browse all 1916

Unable to start Service Bus during initial configuration

$
0
0

System: Windows 7 x64 Enterprise, SQL Server 2008 R2 with full updates.

Web Platform Installer for Workflow Manager 1.0, Service Bus 1.0 with respective cumulative updates and VS 2012 tools.

Account is an administrator and UAC is disabled.

Although I'm getting the error when running the Workflow Manager Configuration Wizard, the problem looks to be the underlying infrastructure. Specifically, the Microsoft.ServiceBus.MessageBroker service host process will start but will not run properly (start and stop via services control panel generates an error). I have followed the same setup on another machine (similar config) and have had no issue.

During Workflow Manager "Configuration Progress" it gets to the point of "Service Bus services starting." and just sits there. After a [very] long time it gives up with a timeout error.

Starting
Created and configured Service Bus farm management database.
Created and configured Service Bus gateway database.
Creating default container.
Microsoft.ServiceBus.Commands.SBFarmInfo

Processing completed
Created and configured farm management database.
Created and configured Workflow Manager resource management database.
Created and configured Workflow Manager instance management database.
Microsoft.Workflow.Deployment.Commands.WFFarmInfo

Processing completed
Validating input and configuration parameters.
Installing auto-generated certificate.
Granting 'Log on as Service' privilege to the run as account.
Windows Fabric configuration started.
Running Windows Fabric deployment.
Windows Fabric starting.
Service Bus configuration started.
Updating database.
Service Bus services starting.
Starting service Service Bus Message Broker failed: Time out has expired and the operation has not been completed.

Log:

[Verbose] [15/06/2013 21:24:32]: Created and configured Service Bus farm management database.
[Progress] [15/06/2013 21:24:32]: Created and configured Service Bus farm management database.
[Verbose] [15/06/2013 21:24:34]: Created and configured Service Bus gateway database.
[Progress] [15/06/2013 21:24:34]: Created and configured Service Bus gateway database.
[Verbose] [15/06/2013 21:24:34]: Configuration added to farm management database.
[Verbose] [15/06/2013 21:24:34]: Generating Certificate.
[Verbose] [15/06/2013 21:24:35]: Service Bus configuration added to the farm management database.
[Verbose] [15/06/2013 21:24:37]: Creating default container.
[Progress] [15/06/2013 21:24:37]: Creating default container.
[Verbose] [15/06/2013 21:24:41]: New-SBFarm successfully completed.
[Info] [15/06/2013 21:24:41]: Microsoft.ServiceBus.Commands.SBFarmInfo

[Info] [15/06/2013 21:24:41]: Processing completed
[Verbose] [15/06/2013 21:24:55]: Created and configured farm management database.
[Progress] [15/06/2013 21:24:55]: Created and configured farm management database.
[Verbose] [15/06/2013 21:24:57]: Created and configured Workflow Manager resource management database.
[Progress] [15/06/2013 21:24:57]: Created and configured Workflow Manager resource management database.
[Verbose] [15/06/2013 21:24:58]: Created and configured Workflow Manager instance management database.
[Progress] [15/06/2013 21:24:58]: Created and configured Workflow Manager instance management database.
[Verbose] [15/06/2013 21:24:58]: Configuration added to farm management database.
[Verbose] [15/06/2013 21:24:58]: Generating certificate.
[Verbose] [15/06/2013 21:24:59]: Workflow Manager configuration added to the Workflow Manager farm management database.
[Verbose] [15/06/2013 21:25:01]: New-WFFarm successfully completed.
[Info] [15/06/2013 21:25:01]: Microsoft.Workflow.Deployment.Commands.WFFarmInfo

[Info] [15/06/2013 21:25:01]: Processing completed
[Verbose] [15/06/2013 21:25:01]: Validating input and configuration parameters.
[Progress] [15/06/2013 21:25:01]: Validating input and configuration parameters.
[Verbose] [15/06/2013 21:25:01]: Installing auto-generated certificate.
[Progress] [15/06/2013 21:25:01]: Installing auto-generated certificate.
[Verbose] [15/06/2013 21:25:06]: Granting 'Log on as Service' privilege to the run as account.
[Progress] [15/06/2013 21:25:06]: Granting 'Log on as Service' privilege to the run as account.
[Verbose] [15/06/2013 21:25:07]: Windows Fabric configuration started.
[Progress] [15/06/2013 21:25:07]: Windows Fabric configuration started.
[Verbose] [15/06/2013 21:25:18]: Windows Fabric cluster manifest generated.
[Verbose] [15/06/2013 21:25:18]: Running Windows Fabric deployment.
[Progress] [15/06/2013 21:25:18]: Running Windows Fabric deployment.
[Verbose] [15/06/2013 21:25:19]: Windows Fabric starting.
[Progress] [15/06/2013 21:25:19]: Windows Fabric starting.
[Verbose] [15/06/2013 21:25:19]: Service Bus configuration started.
[Progress] [15/06/2013 21:25:19]: Service Bus configuration started.
[Verbose] [15/06/2013 21:25:23]: Updating database.
[Progress] [15/06/2013 21:25:23]: Updating database.
[Verbose] [15/06/2013 21:25:23]: Service Bus services starting.
[Progress] [15/06/2013 21:25:23]: Service Bus services starting.
[Error] [15/06/2013 21:35:24]: System.Management.Automation.CmdletInvocationException: Starting service Service Bus Message Broker failed: Time out has expired and the operation has not been completed. ---> Microsoft.ServiceBus.Commands.Common.Exceptions.OperationFailedException: Starting service Service Bus Message Broker failed: Time out has expired and the operation has not been completed.
   at Microsoft.ServiceBus.Commands.Common.SCMHelper.StartService(String serviceName, Nullable`1 waitTimeout, String hostName)
   at Microsoft.ServiceBus.Commands.ServiceBusConfigHelper.StartSBServices(String hostName, Nullable`1 waitTimeout)
   at Microsoft.ServiceBus.Commands.AddSBHost.ProcessRecordImplementation()
   --- End of inner exception stack trace ---
   at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action`3 updateProgress)
   at Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.AddSBNode(FarmCreationModel model, Boolean isFirstCommand)

I found the following entry in the event log that is generated each time I attempt to perform the configuration:

Log Name:      Microsoft-Windows-WindowsFabric/Admin
Source:        Microsoft-Windows-WindowsFabric
Date:          15/06/2013 21:35:20
Event ID:      2564
Task Category: General
Level:         Error
Keywords:      None
User:          Machine\Adam
Computer:      Machine
Description:
Throwing coding error - We should have at most two listen points, one for IPv4, the other for IPv6 Common Level Stack Trace:     00000001:40030184( windows_error(487): Attempt to access invalid address.  )    00000001:400101b4( windows_error(487): Attempt to access invalid address.  )    00000001:400a2fa3( windows_error(487): Attempt to access invalid address.  )    00000001:40099d8f( windows_error(487): Attempt to access invalid address.  )    00000001:40090f6c( windows_error(487): Attempt to access invalid address.  )    00000001:40077dc0( windows_error(487): Attempt to access invalid address.  )    00000001:40077d24( windows_error(487): Attempt to access invalid address.  )    00000001:40038a1e( windows_error(487): Attempt to access invalid address.  )    00000001:40038adc( windows_error(487): Attempt to access invalid address.  )    00000001:40037b32( windows_error(487): Attempt to access invalid address.  )    00000001:40038a1e( windows_error(487): Attempt to access invalid address.  )    00000001:40038adc( windows_error(487): Attempt to access invalid address.  )    00000001:40037b32( windows_error(487): Attempt to access invalid address.  )    00000001:40038a1e( windows_error(487): Attempt to access invalid address.  )    00000001:400f2753( windows_error(487): Attempt to access invalid address.  )    00000001:4002e06c( windows_error(487): Attempt to access invalid address.  )    TpPostWork
    RtlRealSuccessor
    BaseThreadInitThunk
    RtlUserThreadStart

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WindowsFabric" Guid="{CBD93BC2-71E5-4566-B3A7-595D8EECA6E8}" />
    <EventID>2564</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>10</Task>
    <Opcode>0</Opcode>
    <Keywords>0x0</Keywords>
    <TimeCreated SystemTime="2013-06-15T20:35:20.768007500Z" />
    <EventRecordID>6791</EventRecordID>
    <Correlation />
    <Execution ProcessID="3196" ThreadID="1844" />
    <Channel>Microsoft-Windows-WindowsFabric/Admin</Channel>
    <Computer>Machine</Computer>
    <Security UserID="S-1-5-21-2314171880-59287625-2169924697-1000" />
  </System>
  <EventData>
    <Data Name="explanation">We should have at most two listen points, one for IPv4, the other for IPv6</Data>
    <Data Name="stackTrace">    00000001:40030184( windows_error(487): Attempt to access invalid address.  )    00000001:400101b4( windows_error(487): Attempt to access invalid address.  )    00000001:400a2fa3( windows_error(487): Attempt to access invalid address.  )    00000001:40099d8f( windows_error(487): Attempt to access invalid address.  )    00000001:40090f6c( windows_error(487): Attempt to access invalid address.  )    00000001:40077dc0( windows_error(487): Attempt to access invalid address.  )    00000001:40077d24( windows_error(487): Attempt to access invalid address.  )    00000001:40038a1e( windows_error(487): Attempt to access invalid address.  )    00000001:40038adc( windows_error(487): Attempt to access invalid address.  )    00000001:40037b32( windows_error(487): Attempt to access invalid address.  )    00000001:40038a1e( windows_error(487): Attempt to access invalid address.  )    00000001:40038adc( windows_error(487): Attempt to access invalid address.  )    00000001:40037b32( windows_error(487): Attempt to access invalid address.  )    00000001:40038a1e( windows_error(487): Attempt to access invalid address.  )    00000001:400f2753( windows_error(487): Attempt to access invalid address.  )    00000001:4002e06c( windows_error(487): Attempt to access invalid address.  )    TpPostWork
    RtlRealSuccessor
    BaseThreadInitThunk
    RtlUserThreadStart
</Data>
  </EventData>
</Event>

The following warning is also present in the System event log, maybe it's of interest?

Log Name:      System
Source:        Schannel
Date:          15/06/2013 21:35:20
Event ID:      36885
Task Category: None
Level:         Warning
Keywords:      
User:          SYSTEM
Computer:      Machine
Description:
When asking for client authentication, this server sends a list of trusted certificate authorities to the client. The client uses this list to choose a client certificate that is trusted by the server. Currently, this server trusts so many certificate authorities that the list has grown too long. This list has thus been truncated. The administrator of this machine should review the certificate authorities trusted for client authentication and remove those that do not really need to be trusted.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
    <EventID>36885</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2013-06-15T20:35:20.903015200Z" />
    <EventRecordID>175845</EventRecordID>
    <Correlation />
    <Execution ProcessID="684" ThreadID="752" />
    <Channel>System</Channel>
    <Computer>Machine</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
  </EventData>
</Event>

Get-SBFarm output:

FarmType                      : SB
SBFarmDBConnectionString      : Data Source=Machine;Initial
                                Catalog=SbManagementDB;Integrated
                                Security=True;Encrypt=False
ClusterConnectionEndpointPort : 9000
ClientConnectionEndpointPort  : 9001
LeaseDriverEndpointPort       : 9002
ServiceConnectionEndpointPort : 9003
RunAsAccount                  : Adam
AdminGroup                    : BUILTIN\Administrators
GatewayDBConnectionString     : Data Source=Machine;Initial
                                Catalog=SbGatewayDatabase;Integrated
                                Security=True;Encrypt=False
HttpsPort                     : 9355
TcpPort                       : 9354
MessageBrokerPort             : 9356
FarmCertificate               : Thumbprint:
                                7AA4EAB28A748E3FFBF9DA9FE534D7509E09CEF5,
                                IsGenerated: True
EncryptionCertificate         : Thumbprint:
                                7AA4EAB28A748E3FFBF9DA9FE534D7509E09CEF5,
                                IsGenerated: True
Hosts                         : {Name: Machine, Configuration State:
                                HostConfigurationStarted}

IPConfig output

Windows IP Configuration

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::7c68:575f:bfc4:ec24%11
   IPv4 Address. . . . . . . . . . . : 192.168.0.10
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

Tunnel adapter isatap.{4CDAB3A4-D315-4779-9E00-F46FF656C3FD}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:3851:1c62:3f57:fff5
   Link-local IPv6 Address . . . . . : fe80::3851:1c62:3f57:fff5%13
   Default Gateway . . . . . . . . . : ::


If anyone could shed any light on the issue I'd appreciate it! Thanks in advance.


Viewing all articles
Browse latest Browse all 1916

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>