PRB: XLANG Scheduler Shuts Down Even If Database Is Not Available (312666)
The information in this article applies to:
- Microsoft BizTalk Server 2000
- Microsoft BizTalk Server 2002
This article was previously published under Q312666 SYMPTOMS
When the group manager receives a shutdown call, BizTalk Server shuts down schedules that are running, even if the persistence database is not available.
If the group manager receives a shutdown call when the persistence database is not available, the following error is logged in the Event Viewer:
Event Type: Error
Event Source: XLANG Scheduler
Event Category: Engine
Event ID: 12322
Date: 11/27/2001
Time: 11:30:43 AM
User: N/A
Computer: BIZTALKSERVER
Description:
The state of the schedule instance could not be saved to the database.
Detailed information is provided in the following message.
Module name: test
Module ID: {C4CFF181-B546-4519-9351-8F4F6CB540E4}
Instance ID: {CB4A9888-9F2C-4AF2-B9CD-786EE5A68A55}
Database error(s):
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist
or access denied.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen
(Connect()).
Error Code = 0x80004005 : Unspecified error
XLANG Scheduler Engine Internals Information:
File: d:\biztalk_sp1\private\sked\src\runtime\persistence\persist.cpp
Line: 263
This error indicates that the schedules may not have been persisted to the database.
CAUSE
When a shutdown call is made, BizTalk Server tries to shut down all schedules that are running three times at 5 second retry intervals. After three attempts, BizTalk Server sets the internal FORCE_OUT flag. This flag causes group manager to begin to terminate schedules even if they cannot be shut down properly. As a result, each schedule has four opportunities to shut down properly and persist its state to the database.
MORE INFORMATION
A shutdown call is generated through a controlled shutdown or when the BizTalk Server is shut down.
| Modification Type: | Major | Last Reviewed: | 6/4/2003 |
|---|
| Keywords: | kbnofix kbprb KB312666 |
|---|
|