Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: Pooled Interchange Component Never Restores Lost Connection to the BizTalk Document Tracking Database

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

View products that this article applies to.

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: "" { call dta_log_inbound_details( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}"". :'[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

↑ Back to the top

Resolution

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 available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. 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.

↑ Back to the top

Workaround

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

↑ Back to the top

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.

↑ Back to the top

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.

↑ Back to the top

Keywords: KB815321, kbbug, kbfix, kbbiztalk2002sp1fix, kbqfe, kbhotfixserver, kbautohotfix

↑ Back to the top

Article Info
Article ID : 815321
Revision : 8
Created on : 11/15/2007
Published on : 11/15/2007
Exists online : False
Views : 257