Service Bus for Windows Server - API Version Not Supported

Question

I am considering developing an application for working on the premises and outdoors and was hoping to use a service bus for communication between services. I have 2 problems:

• My corporate network is blocking access to my Azure endpoint, so I cannot use my real Azure Service Bus.
• I cannot use WindowsAzure.ServiceBus version 2.2.7.0 for my Windows Server service bus.

I get the following when I try to use the Windows Server service bus (e.g. NamespaceManager.QueueExists):

System.ArgumentException: The remote server responded with an error: (400) Invalid request. The api version in the query string is not supported. Either remove it from Uri, or use one of 2012-03,2012-08,2013-04,2013-07 ...

I suspect that I need to add an api version to NamespaceManager.CreateFromConnectionString, but I just can't find how :(

My current connection string is:

Endpoint = sb: // [my machine] / ServiceBusDefaultNamespace; StsEndpoint = https: // [my machine]: 9355 / ServiceBusDefaultNamespace; RuntimePort = 9354; ManagementPort = 9355

No matter where I write api-version = 2013-07, I do not like it.

MTIA
Andy

Answer 1

Ends here because I get this problem using Service Bus Explorer with Service Bus 1.1 installed locally on my machine.

The problem is related to using the latest version of Service Bus Explorer (currently 2.4.1.1).

The issue was fixed with Service Bus Explorer 2.1, which is also included in the Bus Bus Explorer download.

Using version 2.1.3.0, the problem disappeared.

Get it here. http://code.msdn.microsoft.com/windowsazure/Service-Bus-Explorer-f2abca5a

Edited: Above the link is broken. Use this instead. https://code.msdn.microsoft.com/windowsapps/Service-Bus-Explorer-f2abca5a

Answer 2

You probably encountered some other problems that others had, as in the link below,

http://social.msdn.microsoft.com/Forums/windowsazure/en-US/c23a7c1f-742d-4d7f-ad4f-3bf149964762/service-bus-for-windows-server-the-api-version-is-not- supported? forum = servbus

however, if you notice that there is very little help, except for the following message

http://social.msdn.microsoft.com/Forums/windowsazure/en-US/3aa6c2b8-65ac-4f8b-a36c-674698bb2f41/setting-development-environment-for-service-bus-11-on-windows-7- and-vs-2013? forum = servbus

Quickly reading responses between the lines does not mean using Microsoft.ServiceBus v2.2.0.0, which comes with the Windows Azure SDK 2.2. Instead, take nuget's “Service Bus 1.1 for Windows Server” package and everything should work fine using SB 1.1 for Windows Server.

Answer 3

Install the 1.0 CU Service Bus on the server where Workflow Manager is installed. Refer to: http://support.microsoft.com/kb/2799752 and download it from: https://www.microsoft.com/en-us/download/details.aspx?id=36794

Answer 4

For those who still have this problem, as noted above, the resolution to this problem arose because of a conflict between the Microsoft.ServiceBus assemblies. My project had a link to the ServiceBus DLL that comes with the Azure SDK version 2.7. I replaced the DLL link installed by Service Bus 1.1 and fixed this problem.

Make sure that your builds you are referencing match the correct version.