Installing the Service Bus 1.0 Beta on Windows Server 2012

Recently I created a new virtual machine with Windows Server 2012, SQL Server 2012 and Visual Studio 2012 to try out the new features but I did not really have a purpose for it. After reading the blog post from Richard Seroter about Installing and Testing the New Service Bus for Windows I was very curious whether the Service Bus for Windows Server also works on my freshly installed VM!



The installation process for the Service Bus for Windows Server described in the sections below allows you to install and configure the software on Windows Server 2012.

The installation files of the Service Bus for Windows Server can be found at: 

The Web Platform Installer starts when the installation link is clicked
The Prerequisites dialog appears with a list of prerequisite components that are not
present on the computer
The components are automatically downloaded and installed
To finish the computer must be rebooted at the end of the installation process


Installation of the the Service Bus is is quite straightforward but configuring must be done using PowerShell

Service Bus PowerShell On MSDN is a PowerShell Cmdlets Reference with all the cmdlets that you can use for configuring the Service Bus

First create a new farm with the New-SBFarm cmdlet.
Add the machine to the Farm with the Add-SBHost cmdlet.
Create a new namespace entry in the farm with the New-SBNamespace cmdlet.


Verifying the Configuration

After setup has finished verify that the configuration completed correctly.

Check if the databases are created in SQL Server
Retrieve the Service Bus for Windows Server status with the Get-SBFarmStatus cmdlet
You can also check if the services are running in the Server Manager

Connect to the Service Bus Namespace

The Service Bus Explorer allows users to administer messaging entities in an easy manner. The version provided on the download page for the Service Bus for Windows Server supports the Service Bus 1.0 Beta.
In the “” file is only the sourcecode of the Service Bus Explorer. You can open the solution in Visual Studio 2012 and run it.

First fill in the namespace settings to connect the namespace.

When you connect to the localhost by using a dot, it gets stuck behind the uri so you have to remove it.

Use the PrimarySymmetricKey from the New-SBNamespace result in the “Issuer Secret” field

Click on “Ok” to connect to the namespace

You can find more information about the Service Bus Explorer on:



The installation was very easy. Configuration was slightly harder because a timeout occurred when the host started. First I had to remove the host with “Remove-SBHost” and rebooted the machine before I could add the host again but the second time the “Add-SBHost” cmdlet did the job! :-)

Comments (5) -

10/21/2012 2:57:36 PM #

Hi Tomasso!
Great post, thank you! But I've got an issue while trying to connect using issuer name and secret value. It throws exception with message "The token provider service was not avaliable when obtaining a token for https://n22079:9355/ServiceBusNameSpace/WRAPv0.9/". Inside of this exception there is another inner exception saying that "The remote server returned an error: (404) Not Found."

10/27/2012 12:02:24 PM #


I don't know this error but the Service Bus for Windows Server is now out of Beta and available with an installation wizard. You don't have to use the cmdlets anymore, maybe that will help!

11/1/2012 3:47:56 PM #

"The token provider service was not avaliable when obtaining a token for https://n22079:9355/ServiceBusNameSpace/WRAPv0.9/". Inside of this exception there is another inner exception saying that "The remote server returned an error: (404) Not Found."

I also have the error with the Service Bus 1.0 release.

Any idea?

12/5/2012 1:28:14 PM #

Hi Tomasso. I've got this flat-file buffer, which I want to migrate to Service Bus 1.0. Is this possible ?

12/17/2012 1:04:28 PM #

Hi Isaac,

I do not know the flat-file buffer but if the client can sent a REST message or use the Service Bus API, it should be possible! Wink

Add comment

  Country flag

  • Comment
  • Preview

About the author

Tomasso Groenendijk lives in Netherlands and is a Solution Architect at Insight. He has over 20 years experience in software development and software design. Tomasso is specialized in application integration with a strong interest in the Windows Azure cloud platform. From 2014, Tomasso has been awarded six times with the Microsoft Azure MVP award. He is an active contributor to the integration community through his work on his blog, GitHub samples, TechNet Wiki and speaking on events. Furthermore he is an official board member of the Dutch Microsoft Integration User Group.

MVP profile Tomasso Groenendijk
Sentinet Product Specialist
BizTalk360 Product Specialist

Month List