BizTalk 2013 upgrade fails to register the SB-Messaging schema in the management database
Enrique G. _
9/3/2013 12:00:47 PM
User(s) can reproduce this bug
In the past weeks we finally finished the upgrade of all our environments from BTS 2010 to BTS 2013, the main incentive was a major integration with Salesforce where we could use the new Adapters like WCF-BasicHttpRelay and SB-Messaging. In total we upgraded a total of 14 servers distributed across 5 environments. During the upgrade our QA team performed a regression testing across the environments where no major issues detected for the existing apps.
However, we recently found a couple of issues impossible to detect during the regression tests, here I’m describing the second issue we are having.
Long story short, I arrived to the conclusion that the BizTalk setup when performing an upgrade fails to update BizTalk Management Database with the required schemas for the SB-Messaging adapter. It basically renders the adapter useless making impossible to receive messages from the service bus.
After lot of back and forth trying to figure out what was going on. I started from the simplest thing, just doing a pure routing receive\send port to dump whatever I send to the Azure service bus queues.
Once I put a message in the service bus, immediately BizTalk Errors out, generating a set of around 10 warning messages which basically were a duplicated from the first two ( see below) The warning messages were the typical scenario when a user (or BizTalk in this case) tries to promote some property which schema wasn’t deployed. But the fact that I wasn’t promoting anything (as I said I was doing a pure routing) were telling me that BizTalk was trying to promote some system properties and the schema was missing?! How come? Anyway, I compared the schemas located under the BizTalk.System between two servers one that had been updated and other clean install (I copied and paste them in excel)
Surprisingly, all the other adapter schemas are there except the SB-Messaging. And I have confirmed this issue in all the environments.
So, how can I to fix this?
Error messages after putting a message in the service bus queue
The adapter "SB-Messaging" raised an error message. Details "System.Runtime.InteropServices.COMException (0xC0C01620): Exception from HRESULT: 0xC0C01620
at Microsoft.BizTalk.TransportProxy.Interop.IBTTransportBatch.MoveToSuspendQ(IBaseMessage msg)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.Batch2.MoveToSuspendQ(IBaseMessage message, Object userData)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkReceiveBatch.SuspendMessageIfNeeded(IBaseMessage message, StreamAndUserData streamAndUserData, Int32 messageStatus)".
The adapter "SB-Messaging" raised an error message. Details "System.Exception: Loading property information list by namespace failed or property not found in the list. Verify that the schema is deployed properly.
at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkServiceInstance.EndOperation(IAsyncResult result)
at AsyncInvokeEndEndTwoWayMethod(Object , Object , IAsyncResult )
at System.ServiceModel.Dispatcher.AsyncMethodInvoker.InvokeEnd(Object instance, Object& outputs, IAsyncResult result)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeEnd(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage7(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)".
BizTalk private build 3.9.466.0
Upgrade a server from BTS 2010 to 2013.
to post a comment.
Please enter a comment.
to post a workaround.
Please enter a workaround.
Enrique G. _
Enrique G. _
Enrique G. _
© 2014 Microsoft