SB-Messaging and service bus DLL within BTS seems not compatible with Cloud RRS feed

  • Question

  • I am trying to retreive a message from a Queue in azure service bus. The receive location gets disabled after 5 seconds of enabling it. The error message is :

    The receive location "rlFromFireQueue" with URL "sb://" is shutting down. Details:"System.InvalidOperationException: This client is not supported for a partitioned entity. The client version should be greater or equal than version '2013-10'..8653aa96-4c37-4ee1-8be8-52f2e9702ee0_G2_G2 ---> System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: This client is not supported for a partitioned entity. The client version should be greater or equal than version '2013-10'..8653aa96-4c37-4ee1-8be8-52f2e9702ee0_G2_G2

    I had the same exact issue when I was using an old .Net console application which was using microsft.servicebus.dll version 2.1. I downloaded the 2.4 azure sdk and ran setup. After replacing the reference in my console project to the new version I was able to send messages to my queue.

    My BTS box is 2013 R2 (upgraded from 2013), I checked the directory C:\Program Files (x86)\Microsoft BizTalk Server 2013, I noticed that the Microsoft.ServiceBus.dll in this directory is version 2.1 which according to a thread in blog is not compatible to a new property introduced since last summer ( clients will be updated to support partitioned entities) when creating a new queue using Quick Create.

    So my question is : How can I update the SB-MESSAGING adapter to use a new version to be compatible with this improvments in Azure or more clearly is there any config or procedures to be done to make the bTS 2013R2 adapter compatible with Azure service bus partioning feature

    For your reference, here is the url for the blog where I found the information

    Thanks in advance

    Tuesday, October 7, 2014 9:17 PM


  • I'm afraid you wont be able to update the SB-Messaging adapter because the partitioning option is not supported.

    However you have an alternative:
    You can try using a WCF-Custom port with netMessagingTransport binding. This should be tested, because I'm not 100% sure it supports the partitioning feature. However all necessary features are working because we are using this setup at a current integration project.

    Also be sure to check Paolo's blog for all the necessary information regarding configuration and setup:

    Glenn Colpaert - Microsoft Integration MVP - Blog :

    • Proposed as answer by GlennColpaertMVP Monday, October 13, 2014 9:26 AM
    • Marked as answer by Angie Xu Tuesday, October 14, 2014 1:31 AM
    Wednesday, October 8, 2014 6:10 AM