Hi,

I want to use Service Bus for windows server in intranet scenario for broadcasting messages to all the connected thick clients. I have following questions:

1. I have created subscriber and publisher and I am able to run the application with certificates installed on the client (subscriber's) machine. Is there any way I can have subscribers/clients without having to have certificates installed on them I mean is there anyway we can avoid using https and just use net.tcp/TCP protocol in secure way? If yes could you please show me how to do it?

If I don't install/import certificates on the client machine then I get error in  SubscrptionClient.EndReceive method for certificate. How can I get around this without having to install and use certificates based mechanism.

2. How many subscribers can you have for one topic and performance impact? is there any performance benchmarking done for Service bus for Windows Server? I want to know can this be used in the scenarios like broadcasting events every 1 second to 1000 client?

Thanks

Thanks, Milind

I have a chat application working fine sending and receiving to Windows Service Bus 1.0 (not Azure - this in on-premise windows server version)

I can send/receive my message objects perfectly well using BrokeredMessage through the 1.8 SDK

When I send the exact same object to the same topic using the REST API then my receiver complains that "There was an error deserializing the object of type ServiceBusChat.ChatMessage. The input source is not correctly formatted."

This exception fires at this line in my async receiver 

ChatMessage receivedMessage = message.GetBody<ChatMessage>();

Just to be clear - this listener is working fine when the message is sent through the SDK, but fails when the same BrokeredMessage is sent via the REST API.  (and yes, my POST to the REST API does get a successful 201 created response)

When I look at what is being sent behind the scenes using Fiddler it looks like the SDK serializes BrokeredMessages differently from the built in REST API. I've tried using a BinaryFormatter to deserialize the message stream on the receiver but no joy.   I've also tried binary formatting the message when I send it to the REST API but I can not find a way that works when messages are sent both through the SDK and also through REST API.

Surely it should be possible to send the same messages through SDK or REST API and receive both in the same way?  Or is this something which will be fixed in version 2.0IF that ever gets released for Windows Server?  

(Aside : or have Microsoft abandoned on-premise Windows Server version - the focus seems to be 100% on Azure version now and everything has gone quiet for on-premise Windows Server version)

On example listed under How to integrate a WCF Workflow Service with Service Bus Queues and Topics MSDB article hh709041, is it possible to prepare the messages ICalculatorRequest from the client using ServiceBus API instead of netMessagingBinding?

I'm trying to determine if the messages can be sent either netMessagingBinding or the SDK, and be consumed by service using netMessagingBinding.

We have a service bus relay configured for our on-premise app. We want to turn off load-balancing for this configuration. ie. When the second client tries to listen on the same url, it should throw an exception.

Is there some configuration for this, or is load balancing always on by default?

Thanks,

Hi

I have followed and implemented a service using this example:

http://www.windowsazure.com/en-us/develop/net/how-to-guides/service-bus-relay/

Does anyone know if it is possible to create a client exactly like in the example but in JavaScript instead of C# and basicHttpRelayBinding instead of netTcpRelayBinding? if yes, how?

Best regards

I read several articles about AMQP and how Azure Service Bus supports it and how clients build with Java and other platforms can use Azure Service Bus.

What I cannnot find is what is Microsoft's recommended .NET client that will allow me to use a service bus from a .NET app, without caring if that service bus is the Azure Service Bus or RabbitMQ or other AMQP compliant service bus implementations.

Is Windows Azure SDK and Microsoft.ServiceBus.dll the one that I need? Or that can be used only against Azure Service Bus and not against any AMQP compliant service bus?

Dimitris Papadimitriou, Software Development Professional

I have developed a SOAP web service using .NET that is to be exposed to client applications via a Windows Azure Service Bus relay. The client application that will be calling the SOAP web service is not based on Microsoft technology and the only authentication method that it can support is HTTP Basic authentication over SSL. It cannot support any WS-* web standards. The plan is to use a custom username/password validator in the service configuration to validate the username/password (passed in the HTTP authentication header) against a custom application database.

I'm having real trouble configuring my SOAP web service to use the basicHttpRelayBinding and Basic authentication. In the service configuration I have set the "Security.Mode" property to "Transport", but the relay binding does not support a "ClientCredentialType" property that I can set to "Basic" to specify that the service expects a Basic authentication header. In fact it seems that none of the relay bindings support a "ClientCredentialType" property. This property exists for the standard non-relay WCF bindings (such as basicHttpBinding) and is how you configure Basic authentication.

Have I missed something here, or do the Azure Relay bindings not support HTTP Basic authentication from the client to the service?

Thanks,

Mark.

I see that version 2.0 of the Service Bus has been released onto Azure, but the Windows Server version is still stuck at version 1.0

Does Service Bus have a future for on-premise applications?  Obviously we'd all like to put everything in the Cloud, but real companies have real legacy applications running on-premise and you can't re-write them all in months (or even years).  Our ideal architecture is to use Service Bus to loosely couple legacy applications with new applications as we gradually move to the cloud, but we need to know that this is going to be supported.

Or is Microsoft just throwing all of its energy at Azure and ignoring on-premise applications?

Hi,

Please provide information on how to test Relay Service Bus using Service Bus Explorer. Same query posted in below thread also.

http://social.msdn.microsoft.com/Forums/en-US/windowsazureconnectivity/thread/7eb1cd7c-0f25-4e7c-a46f-7f2853ec45dc

Many Thanks, Thirumalai M

Hello,

I have a WebService who is in charge of creating a record in a database and send a message to Windows Server Service Bus Queue.

I have a using statement with a TransactionScope to enlist the database insert and the message send process.

When I test it, I have the error "Local transactions are not supported with other resource managers/DTC".

Do I need to configure Service Bus and/or DTC to work with this kind of scenario ?

Thanks.

David GROSPELIER Middle-Way - Middleware Senior Architect dgr@middle-way.fr http://www.middle-way.fr

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}

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.

Hi,

Is it possible to use a custom domain on a Service Bus?

Thanks

GilesB

Darek Danielewski BI Software, Inc.

The steps:
In theScheduled Tasks , we get user phone token by search in DB,about5-6million , then push them one by one by Mobile Push Service.

The Issue:

The schedule about Mobile Push Service on Windows Azure often don’t work. And at that time the log recorder also was not enabled.

Sometimes, after waiting a few hours later, the task resume work itself.

All things, JustForU

Does anyone know if Service Bus 1.0 for Windows Server supports AMQP?  If so, is the .NET client library still in preview (as it was in October) / have they been deployed as part of the release API? 

Thanks,

Harin

Hi,

I'm defining a solution for an on-premises task queue that will allow durable, at least and at most once processing of multiple consumers/computers.

The simplest solution would have a been a centralized queue (transactional remote msmq, SQL table and etc) but it won't scale well.

I'm looking for a symmetric scaling out ability of being able to add an identical consumer to the "farm". I've read that the service bus allows only 3 nodes to be part of a highly available farm. How come? Why can't I have 2 or 4 nodes as I understood all message containers are replicated and will keep the data if one of nodes crushes.

Thanks, Rami

i have installed servicebus 1.0 on a virtual server and it appears to have installed correctly and i can see the service running.  I followed all the steps here on msdn. Then on my dev box i setup a visual studio project that is a copy of the "write your first application" @ http://msdn.microsoft.com/en-us/library/windowsazure/jj542433%28v=azure.10%29.aspx

When i run the program i get the following error:

"{"The token provider was unable to provide a security token while accessing 'https://vdev2k8:9355/ServiceBusDefaultNamespace/$STS/Windows/'. Token provider returned message: ''."}"

while searching here i have followed the example on installing the certs on the dev/client machines.  herehttp://msdn.microsoft.com/en-us/library/windowsazure/jj192993%28v=azure.10%29.aspx

if i drill down into the exception i see that i'm getting {"The remote server returned an error: (401) Unauthorized."} as the base exception.

i have not setup anything dealing with users/accounts, access keys/tokens etc.

Here is the output from "get-sbnamespace"

Name                  : ServiceBusDefaultNamespace
AddressingScheme      : Path
CreatedTime           : 3/19/2013 8:54:45 PM
IssuerName            : ServiceBusDefaultNamespace
IssuerUri             : ServiceBusDefaultNamespace
ManageUsers           : {administrator}
DnsEntry              :
PrimarySymmetricKey   : 8DO3lasdfddddddddddddD80HZX0X/4PdXppIK3o=
SecondarySymmetricKey :

any ideas on things that i can try to resolve this issue?

Hi,

Please provide information on how to test Relay Service Bus using Service Bus Explorer. Same query posted in below thread also.

http://social.msdn.microsoft.com/Forums/en-US/windowsazureconnectivity/thread/7eb1cd7c-0f25-4e7c-a46f-7f2853ec45dc

Many Thanks, Thirumalai M

Hi @ll,

I'm not able to get Service Bus running on my Windows Server 2012 x64

The symptom on Service Bus is, that during the Add-SBHost command the Message Broker service gets stuck in endless error loop. 

Microsoft-ServiceBus Event Log entry:
Windows Fabric Runtime create failed (Retries left 1) Exception System.TimeoutException: Operation timed out. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071BFF

Microsoft\Windows\Windows Fabric event log entry:
connection 8dac340 at client failed to connect to send target 13921008, have tried all addresses resolved from localhost:9003

My guess for the root cause:
The "Windows Fabric Lease Layer" device is not able to start properly. In device manager it's shown with a yellow exclamation mark.

In System event log I see the following after installing via WebPI:
Log Name:      System
Source:        Microsoft-Windows-Kernel-PnP
Event ID:      219
Task Category: (212)
Level:         Warning
Description:
The driver \Driver\leaslayr failed to load for the device ROOT\SYSTEM\0001.

But there are no details in the event log why this device isn't able to start (Windows Fabric-Lease is empty. Enabling Debug & Analytic won't help either). So this is where I'm stuck at the moment...

Before you start asking: It's not the firewall. Firewall is deactivated and ports are working fine in a test application. Even netstat -aon shows they are available.

Hosts file is also empty.

Thanks for any hints you have to offer :-)

~Thomas

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}

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.