Microsoft Knowledge Base Email Alertz

When the group manager receives a shutdown call, BizTalk Server shuts down schedules that are running, even if the persistence database is not available.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 312666 - Last Review: June 4, 2003 - Revision: 2.2

PRB: XLANG Scheduler Shuts Down Even If Database Is Not Available

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.

APPLIES TO
  • Microsoft BizTalk Server 2000 Standard Edition
  • Microsoft BizTalk Server 2002 Standard Edition
Keywords: 
kbnofix kbprb KB312666
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate