Back to the future - Microsoft.XLANGs.Core.TimeoutException

I recently faced this not so welcome friend of mine. This was the case on mine development environment consisting of:

- separate BizTalk machine + separate SQL Server

I could track down the source of this message being an atomic scope with a timeout of 60 seconds (receive shape waiting for a web service response). Since the error was pretty clear i finally found the cause….please take note of this for future generations ;)

The SQL Server machine clock was advanced 2 minutes compared to the BizTalk server running the orchestrations

Therefore the orchestration was ‘running in the past’ forcing a time-out in the atomic scope shape.

Somehow the time synchronisation service was not doing it’s job. I fixed the issue by using the ‘w32tm’ command line tool.

“w32tm /resync” (force the machine to resync the windows time using the PDC time)

Note: to view the difference between the current machine and the PDC you can you the monitor parameter;

“w32tm /monitor”

Comments

Post a Comment

Popular posts from this blog

Azure implementation guidelines

In My post ‘ Service Bus Management ’ I pointed out a way of implementing a DTAP strategy for managing the Service Bus environment. There’s now a great post available from Microsoft which goes into more detail about other aspects of managing the Azure subscriptions and other artefacts which is quite useful when setting up your Azure environments. Follow this link to the ‘Azure Implementation Guidelines’ HTH, Sander
Read more

Focus and innovation - recap of the last 2 years

It's been a long time since my last post. Hereby a partial explanation for that, with the note that this blog will remain active for the purpose of being a resource for historical references. My IT career started with programming, and adventures within holland, as well as overseas. When I realised programming is something you can specify, I figured that providing added value is crucial for a long term career and decided to focus on process centric roles. I started with webservice integration and eventually from that to process integration using BizTalk. The great feeling when discussing high level processes and implementing solutions within days, even highly scalable and interfacing with LOB systems is great. After several years of implementing solutions like these, I started questioning if all of this work was justified by the business case, if the solution was actually contributing, if the choices had been valid. In other words, I needed to understand the choices made. When...
Read more

BizTalk Pub/sub vs Topics based routing–discussion

My colleagues and I had a brief discussion about the subject ‘Topics’ and what it brings… Do you all agree/disagree with the following statement: topic-based pub-sub messaging doesn’t really exist in BizTalk “In my opinion; I disagree, as BizTalk offers the following 'out-of-the-box' • Message Routing (f.e build in context properties like message type, trading partner, operation etc) • Content Routing (f.e. promoted properties, message inspection in orchestrations/pipelines icw orchestration logic)” My colleague Rene Brauwers Here my 2 cents…. I agree that it exists...however the current offerings in BizTalk are tightly coupled, making the usage far from perfect. When doing content based routing on custom fields (promoted properties), you will be making the solution message-coupled; Your custom message property schema is deployed, and the message filter on these fields have a direct relationship with this property schema. Making any change to this schema will g...
Read more