Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Biztalk 2009 Losing orchestrations…
- This topic has 2 replies, 1 voice, and was last updated 9 years, 3 months ago by
community-content.
-
AuthorPosts
-
-
July 23, 2009 at 3:40 PM #22905
Hi,
I experienced something quite scary today. We have a main orchestration which on receipt of a WCF service call, calls a number of sub orchestrations, which in parallel go away and get information that is then aggregated and returned as a response to the original service call.
This deployed, configured and ran successfully for a few days, until today that is.
The calling app was returning an internal error. On examination of the Application event log we see
<<The Messaging engine failed to process a message submitted by adapter:WCF-BasicHttp Source URL:/xxx.svc. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure.
I then went into the application in the Biztalk Admin console and saw that some of the orchestrations had simply disappeared, they were no longer in the list!!! I had to re-deploy to get them to re-appear.
Has anyone seen this?
As an aside, we’ve also found that sometimes references to other projects simply disappear and you have to remove them and re-add them as references. We’ve got around this by making sure that no orchestration .odx file is open when we compile.
This is my first foray into Biztalk, but based on my experiences so far, it seems a little flaky…
Thoughts anyone?
regards
Kindo
-
December 15, 2009 at 12:22 PM #23904
I have seen this only when publishing from VST.
-
December 15, 2009 at 8:16 PM #23907
Hi Kindo,
It sounds like you are deploying your orchestrations (and related artifacts) projects directly from your Visual Studio developer environment to your production box, which you should NOT do.
Check out the following articles for recommended best practices on how to develop and administer BizTalk applications:
http://msdn.microsoft.com/en-us/library/aa577468(BTS.20).aspx
http://msdn.microsoft.com/en-us/magazine/cc163423.aspx
These best practices will save you from getting a lot of headaches and heartaches (not to mention visits from your boss and bad marks on your performance reviews)… Trust me… 🙂
Daniel.
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.