Article ID: 884565 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
On a computer that is running Microsoft BizTalk Server 2004, both of the following events may be logged in the Application log:
Event Type: Error
Event Type: Warning
This problem occurs if a deadlock condition occurs in Microsoft SQL Server 2000. In BizTalk Server 2004, a race condition may occur during the message dequeuing process. This race condition could lead to a thread deadlock condition in SQL Server 2000.
Service pack informationTo resolve this problem, obtain the latest service pack for BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/888751/ )How to obtain the latest BizTalk Server 2004 service pack
PrerequisitesNo prerequisites are required to install this hotfix.
Restart requirementYou do not have to restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Date Time Version Size File name ---------------------------------------------------------------------------- 12-Aug-2004 02:27 3.0.5327.0 217,088 Microsoft.xlangs.biztalk.engine.dll
Hotfix installation informationThis hotfix is only intended to resolve the race condition that is mentioned in the "Cause" section. Do not install this hotfix to try to resolve other issues that you might experience, such as a low-latency issue.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was corrected in BizTalk Server 2004 Service Pack 1.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 884565 - Last Review: January 17, 2015 - Revision: 3.1