BizTalk Development's Secret of restarting BizTalk hosts

When you unbind a business process from BizTalk Server Browser, it is recommended that you remove and stop all dependencies, including the BizTalk Server host. You want to know why you have to do the damn thing-stop the mainframe.

The answer is simple. Unless the whole. NET application is uninstalled, otherwise. NET Framework does not unload a separate assembly from the application domain. This means that you have to reboot the host in order to uninstall the assembly. To avoid the added confusion of outdated assemblies, BizTalk Server Browser provides a quick way to restart the host to facilitate the reconfiguration of the Orchestration Assembly. However, if you need to rearrange the pipeline or the schema assembly, there will be no "quick Unbind" dialog box, and you may receive a bunch of annoying error messages in the application event (I received a lot of ^_^):

• Error executing receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "XML disassembler". Reason: Loading document specification ... "
• or "The Messaging engine has been suspended from the adapter because of an error in message handling ..."
• or other errors that occur frequently in microsoft.public.biztalk.general or BizTalk-related discussion groups.

So, if you've had this annoying error message after you've just reinstalled the assembly, don't bother to find out why, restart the mainframe, maybe it's all settled.

The original text reads as follows:

Restarting BizTalk host.
When you are unenlist orchestration in BizTalk Server Explorer, it kindly suggests you to unenlist and stop all dependencies I ncluding BizTalk Server Host. Did you ever wonder about why does that darn thing are asking to stop the host?

The answer is simple. . Net Framework doesn ' t provide mean to unload separate assembly from application Domain–only whole app domain could is U Nloaded. BizTalk server Host is a. Net process this loads assemblies in main app domain. This is means to unload assembly your have to restart the host. So, for avoiding extra confusions caused by outdated assemblies loaded by BizTalk Host–biztalk Server Explorer provides Quick way of restarting the host and thus, smoothes redeployment of orchestration Assembly. However, if you are need to redeploy pipeline or schemas assembly–there are no such helpful "Express unenlist" dialog box, an D you could with a bunch the wired error messages in application event log like:

·“ There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "XML Disassem Bler ". Reason:loading Document Specification ... "

· Or "The messaging Engine has suspended" 1 "message (s) due to outbound processing. Please use Health and Activity tracking to determine the cause of this failure.

· or other equally cryptic error messages this you often can, posted in microsoft.public.biztalk.general and other biztal K Server related groups.

So, if you have some weird error message right after your redeploy some assembly, don ' t panic and try to restart the host– It may help.

Description: This article gives me a lot of help, I believe that the BizTalk beginners will also have a great help, so special translation. However, when you encounter this situation, you can restart the BizTalk Server application in Service Manager before restarting the host and try again.

For the host that appears in the text, I translated as the mainframe, I do not know the original author refers to the host program or hosting, the first translation, please advise.

Original URL http://www.harper.no/valery/PermaLink,guid,8360fa2a-2ffa-4085-84a4-d7cdaae9f80b.aspx