Geeks With Blogs
Simon Emmanuel RIVAS December 2013 Entries
BizTalk 2013: Connection timeout when integrating with Azure Service Bus
In the last few months, I have read a few excellent posts about BizTalk integration with Azure Service Bus (especially this one from Steef-Jan Wiggers and more recently this one from Paolo Salvatori) and successfully followed the instructions, thus managing to send and receive data from the Service Bus. Knowing that I did it at least once on another BizTalk 2013 box, I was pretty confident when a few weeks ago I was asked to quickly demonstrate how one can integrate BizTalk with a Service Bus Queue. ......

Posted On Friday, December 13, 2013 10:03 AM

BizTalk Log Shipping across different domains: SSO fails to start
The Log shipping mechanism implemented in BizTalk works pretty well in a homogeneous environment, but a few details have to be taken care of when production and DR domains differ, or more generally when security groups differ. Switching to the Disaster Recovery site: the theory Let’s focus on the SSO part. Here is a basic, macro overview of the steps you would take to switch to the DR site: Restore the production databases on the DR SQL Server Make sure the UpdateInfo.xml is OK (which can be found ......

Posted On Thursday, December 5, 2013 1:21 PM

BizTalk side-by-side versioning: “Loading property information list by namespace failed or property not found in the list” when enlisting an orchestration
The above error message is well known and is usually related to a property schema simply not being deployed, and it is usually raised in send or receive pipelines. But actually it could happen if you (re)deploy different versions of the same property schema in the wrong order (ie: an older version after a newer version). How could it ever happen? This is a legitimate question you might want to ask: “Why would someone want to deploy an older version AFTER a newer version of a property schema in the ......

Posted On Wednesday, December 4, 2013 6:17 PM

ESB times out when resubmitting a message
Never overlook any property, this is the conclusion I have come to after diagnosing a tricky bug…Here is what happened. Scenario I had an orchestration orchA that consumed messages submitted by a one-Way HTTP receive port, which routed a transformed copy of the message to another orchestration orchB. When an error occurred in orchB, an ESB fault was generated with the input message attached to it and the fault was then sent to the ESB Exception Db. A classical error handling scenario… When resubmitting ......

Posted On Tuesday, December 3, 2013 10:27 AM

Copyright © S.E.R. | Powered by: