It's a strange mistake!
Install the BTS component in the production environment. Instead of using VS2005 for deployment, you can directly use the BizTalk Admin tool!
Start the test.
After receiving the specified message, BTS reports an error!
Event Type: Error
Event Source: BizTalk Server 2006
Event Type: BizTalk Server 2006
Event ID: 5719
Date: 2008-3-31
Event: 11:46:29
User: N/
COMPUTER: GDEIAC-BIZ01
Description:
An error occurred while executing the receiving pipeline: "Microsoft. bizTalk. defaultPipelines. XMLReceive, Microsoft. bizTalk. defaultPipelines, Version = 3.0.1.0, Culture = neutral, PublicKeyToken = 31bf3856ad364e35 ", source:" XML disassembling ", receiving port:" R_OA_NS_MSG ", URI:" FORMATNAME: DIRECT = TCP: 10.16.25.81 \ PRIVATE $ \ NS_MESSAGE ", cause: Unable to migrate from Assembly <EIAC. OA. icationicationsystem. schemas, Version = 1.0.0.0, Culture = neutral, PublicKeyToken = faf62f0e1206ebb8> document loading specifications <EIAC. OA. icationicationsystem . Schemas. icationicationdata_xml>. Verify that the architecture of this document specification has been deployed and that the architecture is in the Global Assembly Cache.
Event Type: Error
Event Source: BizTalk Server 2006
Event Type: BizTalk Server 2006
Event ID: 5753
Date: 2008-3-31
Event: 11:46:29
User: N/
COMPUTER: GDEIAC-BIZ01
Description:
The message received by the adapter "MSMQ" at the "R_OA_NS_MSMQ_Message" (URI is "FORMATNAME: DIRECT = TCP: 10.16.25.81 \ PRIVATE $ \ NS_MESSAGE") has been suspended.
Error details: An error occurred while executing the receiving pipeline: "Microsoft. bizTalk. defaultPipelines. XMLReceive, Microsoft. bizTalk. defaultPipelines, Version = 3.0.1.0, Culture = neutral, PublicKeyToken = 31bf3856ad364e35 ", source:" XML disassembling ", receiving port:" R_OA_NS_MSG ", URI:" FORMATNAME: DIRECT = TCP: 10.16.25.81 \ PRIVATE $ \ NS_MESSAGE ", cause: Unable to migrate from Assembly <EIAC. OA. icationicationsystem. schemas, Version = 1.0.0.0, Culture = neutral, PublicKeyToken = faf62f0e1206ebb8> document loading specifications <EIAC. OA. notificati OnSystem. Schemas. icationicationdata_xml>. Verify that the architecture of this document specification has been deployed and that the architecture is in the Global Assembly Cache.
Message ID: {1403920C-8604-4B05-AFBA-7372E4B2220C}
Instance ID: {E461A125-C380-497C-9152-CB60EC744B88}
Query GAC
Check the Assembly directory
They are all normal !!!! Strange !!
Solution:
After restarting the server, the current phenomenon is gone! Very strange! A good explanation is not found.
Your own guesses:
Because I created a separate Host Instance for this process, and the Receive Adapter still uses BizTalkApplicationHost, the default Host also needs to be restarted to load it to the newly registered Dll.