Microsoft KB Archive/838874

= FIX: BizTalk Server continuously restarts itself =

Article ID: 838874

Article Last Modified on 5/15/2006

-

APPLIES TO


 * Microsoft BizTalk Server 2002 Standard Edition
 * Microsoft BizTalk Server 2002 Service Pack 1

-





SYMPTOMS
When the log file for the InterchangeDTA database is full, Microsoft BizTalk Server continuously restarts itself. You may see multiple instances of the following errors and events in the application event log:

An error occurred in BizTalk Server.

Details: --

[0x1625] An error occurred in BizTalk Server.

Details: --

The following stored procedure call failed: &quot; { call dta_log_inbound_details( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}&quot;. :'The log file for database 'InterchangeDTA' is full. Back up the transaction log for the database to free up some log space.' Changes could not be committed to the database.

[0x1916] There was a serious failure in the receive function &quot;Test&quot;. 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 &quot;(null)&quot;. This receive service will be shut down, please check the event log for additional error messages.

An error occurred in BizTalk Server.

Details: --

[0x80040e14] The following stored procedure call failed: &quot; { call dta_log_inbound_details( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}&quot;. :'The log file for database 'InterchangeDTA' is full. Back up the transaction log for the database to free up some log space.'

[0x1625] Changes could not be committed to the database.

[0x1730] Suspended Queue ID: &quot;{B23660E8-DDE5-4E17-AE07-312DA0A674FC}&quot;

[0x1625] Changes could not be committed to the database.

An error occurred in BizTalk Server.

Details: --

[0x1711] The server is shutting down because of a database failure.

The service has started.

This loop continues until the system runs out of resources and BizTalk Server stops responding. The InterchangeDTA database grows huge.



RESOLUTION
A 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 phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;[LN;CNTACTMS]

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.  Date        Time   Version     Size     File name --  01-Apr-2004  22:44  3.0.2522.0  368,912  Mscis.exe Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.



MORE INFORMATION
After you apply this hotfix, if the InterchangeDTA log file is full, BizTalk Server restarts itself with a backoff algorithm. BizTalk Server tries to restart itself in 1, 2, 4, 8, 16, 32, 60, 60, and 60 minutes until BizTalk Server succeeds and runs fine for 5 minutes. BizTalk Server must run for at least 5 minutes before the backoff progression is reset back to 1 minute. This backoff algorithm gives the users and administrators time to discover the database log file issue and deal with it.

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

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbbug kbfix kbhotfixserver KB838874

-

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

© Microsoft Corporation. All rights reserved.