Microsoft KB Archive/321877

= INFO: BizTalk Messaging Service Enters a Paused State After Unexpected Database Failure or Network Problem =

Article ID: 321877

Article Last Modified on 1/14/2003

-

APPLIES TO


 * Microsoft BizTalk Server 2002 Standard Edition

-



This article was previously published under Q321877



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SUMMARY
If BizTalk Server 2002 loses connectivity to its messaging databases because of an unexpected database failure or network problem:
 * After the initial loss of connectivity, the BizTalk Messaging Service enters a &quot;paused&quot; state for one minute, and then it tries to restart itself.
 * If the first restart attempt fails, the BizTalk Messaging Service enters a paused state for twice as long as it did previously (two minutes in this case) before it tries to restart. If subsequent attempts to restart fail, BizTalk continues to double the length of time during which it is in a paused state up to a maximum time of one hour. The BizTalk Messaging Service continues to cycle between pausing and trying to restart until it successfully restarts.

You can configure the maximum pause state interval through the registry entry that is listed in the &quot;More Information&quot; section in this article.

Additionally:  While the BizTalk Messaging Service is paused, it does not engage in any message processing but it does accept shutdown messages, so you can manually stop and start the BizTalk Messaging Service while it is in a paused state. To determine if the BizTalk Messaging Service is in a paused state, check the status of the BizTalk Messaging Service from the Service Control Manager. To access Service Control Manager, open the Administrative Tools folder and then double-click Services. If at any point the BizTalk Messaging Service successfully restarts, the next time it loses connectivity the pause state interval is reset to one minute. The BizTalk Messaging Service does not shut down and enter a paused state during a database deadlock, a stored procedure timeout, or a DTC timeout. The BizTalk Server 2002 Messaging Service can handle these types of errors without having to restart.  When BizTalk Server enters the paused state and tries to restart, the BizTalk Server Application log contains entries with a description of &quot;The service is restarting&quot; at the following intervals: +==================+=====================+===================+ +==================+=====================+===================+ +==================+=====================+===================+ +==================+=====================+===================+ +==================+=====================+===================+ +==================+=====================+===================+ +==================+=====================+===================+ +==================+=====================+===================+ +==================+=====================+===================+ +==================+=====================+===================+ These intervals do not follow the expected intervals of 0, 1, 2, 4, 8, 16, 32, and 60 minutes because at the end of every pause interval, BizTalk Server Messaging may spend up to 30 minutes trying to restart before it enters a paused state again.  When BizTalk Server Messaging enters a paused state, it logs the event log entry &quot;The service is restarting.&quot; This occurs because no event log entry was created to indicate that the Messaging Service paused when this functionality was created. The stop, pause, and restart routine does not work correctly on &quot;Receive only&quot; servers. This issue is addressed in the hotfix that is described in Q321950.</li> This functionality only applies to BizTalk Messaging, and not to BizTalk Orchestration.</li> BizTalk Server 2000 immediately tries to restart if an unexpected database failure or network problem occurs and it cannot enter a paused state; it may attempt to restart in some cases where BizTalk Server 2002 does not.</li></ul>
 * Elapsed Minutes | Interval in Minutes | Status            |
 * 0               | 0                   | Trying to Restart |
 * 1               | 1                   | Paused            |
 * 31              | 30                  | Trying to Restart |
 * 33              | 2                   | Paused            |
 * 63              | 30                  | Trying to Restart |
 * 67              | 4                   | Paused            |
 * 97              | 30                  | Trying to Restart |
 * 105             | 8                   | Paused            |

<div class="moreinformation_section">

MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

You can configure the maximum pause time (the time that BizTalk Server waits before attempting to restart) by making the following modification to the registry: <ol> Start Registry Editor (Regedt32.exe).</li> Locate, and then click the following key in the registry:

 

</li> On the Edit menu, click Add Value, and then add the following registry value to configure the retry interval:

Value name: MaxRestartDelay

Data type: REG_DWORD

Radix: Decimal

Value data:

</li> Quit Registry Editor.</li></ol>

When the BizTalk Server Messaging Service shuts itself down, pauses, and attempts to restart, messages that are similar to the following are written to the BizTalk Server Application log:

<pre class="fixed_text">Event Type: Error Event Source:  BizTalk Server Event Category: Document Processing Event ID:  324 Date:      4/26/2002 Time:      11:23:02 AM User:       N/A Computer:  BIZTALKSERVER Description: An error occurred in BizTalk Server. Details: -- [0x1711] The server is shutting down because of a database failure.

--

<pre class="fixed_text">Event Type: Error Event Source:  BizTalk Server Event Category: Document Processing Event ID:           324 Date:      4/26/2002 Time:      11:23:02 AM User:       N/A Computer:           BIZTALKSERVER Description: An error occurred in BizTalk Server. Details: -- [0x80004005] The following stored procedure call failed: &quot; { call cs_get_next_WorkQ( ?, ?, ?, ?)}&quot;. :'[DBNETLIB][ConnectionWrite (WrapperWrite).]General network error. Check your network documentation. [0x0128] The next scheduled work item cannot be obtained for processing.

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

--

<pre class="fixed_text">Event Type: Information Event Source:  BizTalk Server Event Category: BizTalk Server 2002 Event ID:           352 Date:      4/26/2002 Time:      11:23:02 AM User:       N/A Computer:           BIZTALKSERVER Description: The service is restarting.

Keywords: kbinfo KB321877

-

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

© Microsoft Corporation. All rights reserved.