Microsoft KB Archive/815321

= FIX: Pooled Interchange Component Never Restores Lost Connection to the BizTalk Document Tracking Database =

Article ID: 815321

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2002 Standard Edition

-





SYMPTOMS
After a connection interruption between the computer that is running BizTalk Server and the computer that is running Microsoft SQL Server, you may receive the following error message when you call IInterchange::Submit or IInterchange::SubmitSync:

An error occurred in BizTalk Server.

The following stored procedure call failed: &quot;&quot; { call dta_log_inbound_details( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}&quot;&quot;. :'[DBNETLIB][ConnectionWrite (WrapperWrite).]General network error. Check your network documentation.'

After a connection loss to the computer that is running SQL Server, you cannot build error routines to trap the error and resubmit the initial failed submission. Instead, you must restart the Interchange COM+ application to resolve the problem.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

331337 Must Restart the Interchange COM+ Application After a Connection Loss to SQL



Service 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 Information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

The English version of this fix 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.   Date         Time   Version     Size    File name --  01-Mar-2003  00:18  3.0.1563.0  53,520  Dbaccessor.dll Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.



WORKAROUND
To work around this problem, disable the object pooling of the Interchange COM+ component.



STATUS
Microsoft 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.



MORE INFORMATION
Note: Installation of the individual hotfix will restart BizTalk, but you may have to restart the whole server if the related files are locked.

Keywords: kbhotfixserver kbqfe kbbiztalk2002sp1fix kbfix kbbug KB815321

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.