Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 298728 - Last Review: October 17, 2003 - Revision: 3.1
PRB: Documents Processed by BizTalk Server Appear Stuck in Work Items Queue
This article was previously published under Q298728
When you submit a document for processing by Microsoft BizTalk Server, the document may not move out of the Work Items queue, and the following informational messages may appear in the Application log of the BizTalk Server:
Event Type: Information
Event Source: MSDTC Client
Event Category: CM
Event ID: 4156
Date: 5/2/2001
Time: 1:28:38 PM
User: N/A
Computer: <ServerName>
Description:
String message: INFORMATIONAL : CSO::Maintain_SSTATE_UP session Failed ProcID=0x5c0 Error =0x80004005.
Event Type: Information
Event Source: MSDTC
Event Category: CM
Event ID: 4156
Date: 5/2/2001
Time: 1:28:47 PM
User: N/A
Computer: <ServerName>
Description:
String message: ProcId = 0x1e4 CSO: Maintain session; Received E_CM_SERVER_NOT_READY.
This problem can occur if the Microsoft Distributed Transaction Coordinator (MS DTC) Globally Unique Identifier (GUID) for BizTalk Server matches the MS DTC GUID on the remote Microsoft SQL Server computer that houses the BizTalk Server InterchangeBTM database.
Uninstall and reinstall the MS DTC on the BizTalk Server and the SQL Server. For additional information on how to do this, click the article number below
to view the article in the Microsoft Knowledge Base:
246679Â
(http://kbalertz.com/Feedback.aspx?kbNumber=246679/EN-US/
)
BUG: DTC Remote Coordinator Fails After DTC Is Configured for an Invalid Remote Host Name
This behavior is by design.
The MS DTC GUID for two Windows 2000 servers is always unique unless the operating systems on these computers were created with ghosting software.
APPLIES TO
- Microsoft BizTalk Server 2000 Standard Edition
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate