FIX: BizTalk May Return a DTC Timeout on Non-Transactional Receive Functions (818137)
The information in this article applies to:
- Microsoft BizTalk Server 2002
- Microsoft BizTalk Server 2000 SP2
SYMPTOMSWhen you run Microsoft BizTalk Server in an environment that uses transactional receive functions and non-transactional receive functions, you may receive the following error messages in the event log for the non-transactional receive functions:Event Type:
Error Event Source: BizTalk Server Event Category: (2) Event ID:
324 Date: 1/28/2003 Time: 2:35:09 PM User: N/A Computer:
Microsoft Description: An error occurred in BizTalk Server.
Details: ------------------------------ [0x1916] There was
a serious failure in the receive function "Receive File". This receive service
will be shut down, please check the event log for additional error messages.
[0x80004005] Unspecified error
[0x172d] The receive
function "Receive File" has experienced problems, it will be shut down and
disabled. Once these problems have been corrected, re-enable this receive
function in BizTalk Server Administration.
[0x1704] There was a
failure processing the "Receive File" receive function. Check your receive
function configuration in BizTalk Server Administration.Event Type: Error Event Source: BizTalk
Server Event Category: (2) Event ID: 324 Date: 1/28/2003
Time: 2:35:07 PM User: N/A Computer: Microsoft Description:
An error occurred in BizTalk Server.
Details:
------------------------------ [0x011e] An error occurred in BizTalk
Server.
Details: ------------------------------ The
following stored procedure call failed: " { call dta_log_inbound_details( ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}". :'Distributed transaction completed.
Either enlist this session in a new transaction or the NULL transaction.'
Changes could not be committed to the database.
Suspended Queue ID:
"{C92608F4-A2C7-4812-88C1-5127A7EAD764}"
Changes could not be
committed to the database.
The following stored procedure call
failed: " { call cs_create_SuspendedQ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}".
:'Distributed transaction completed. Either enlist this session in a new
transaction or the NULL transaction.' A new work item in the Suspended queue
cannot be created.
[0x1916] There was a serious failure in the
receive function "Receive File". This receive service will be shut down, please
check the event log for additional error messages. [0x1916] There was a
serious failure in the receive function "(null)". This receive service will be
shut down, please check the event log for additional error
messages.RESOLUTIONService Pack Information
To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2002. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
815781 How to Obtain the Latest BizTalk
Server 2002 Service Pack
Hotfix InformationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem. To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) 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.
BizTalk Server 2002 Date Time Version Size File name
---------------------------------------------------------------
07-May-2003 01:11 3.0.1571.0 172,304 Biztalkhttpreceive.dll
07-May-2003 01:11 3.0.1571.0 131,344 Cisapi.dll
07-May-2003 01:11 3.0.1571.0 528,656 Ciscore.dll
07-May-2003 01:11 3.0.1571.0 254,224 Cisdta.dll
07-May-2003 01:11 3.0.1571.0 409,872 Cisengine.dll
07-May-2003 01:10 3.0.1571.0 53,520 Dbaccessor.dll
07-May-2003 01:11 3.0.1571.0 352,528 Mscis.exe Note For each computer that is running BizTalk Server 2002, and for
each database group, you must run Btm_priorityupgrade.sql against the BizTalk
Interchange_BTM database, and you must run Sq_priorityupgrade.sql against the
BizTalk Interchange_SQ database. To do so, you must use the Microsoft SQL Query
Analyzer to run the stored procedures against the affected BizTalk database. BizTalk Server 2000 Date Time Version Size File name
------------------------------------------------------
17-Apr-2003 02:03 2.0.2007.0 205,072 Cisapi.dll
03-Oct-2003 20:34 2.0.2010.0 688,400 Ciscore.dll
17-Apr-2003 02:04 2.0.2007.0 360,720 Cisdta.dll
17-Apr-2003 02:04 2.0.2007.0 549,136 Cisengine.dll
17-Apr-2003 02:04 2.0.2007.0 393,488 Mscis.exe Note Because of file dependencies, the most recent hotfix or feature
that contains these files may also contain additional files. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Microsoft
BizTalk Server 2002 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 10/17/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbBizTalk2002SP1fix kbfix kbbug KB818137 |
---|
|