Microsoft KB Archive/317083

From BetaArchive Wiki
Knowledge Base


FIX: The Error "All Submit Calls Have Been Blocked Due to a Database Failure" Occurs After a Clustered Database Failover

Article ID: 317083

Article Last Modified on 10/22/2003



APPLIES TO

  • Microsoft BizTalk Server 2000 Standard Edition



This article was previously published under Q317083

SYMPTOMS

If you fail over a clustered database that houses the tables that the BizTalk Messaging Service requires, the BizTalk Messaging Service may stop processing documents until you stop and restart the BizTalk Server Interchange Application COM+ application.

If this problem occurs, the following error message is logged in the BizTalk Server Application log:

An error occurred in BizTalk Server.

Details:



All submit calls have been blocked due to a database failure. After correcting this problem, please go to Component Services and shut down the 'BizTalk Server Interchange Application', before attempting to call any submit method.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

299664 INFO: How to Obtain the Latest BizTalk Server 2000 Service Pack


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 2000 Service Pack 2.

MORE INFORMATION

BizTalk Server cannot continue processing documents if the connection to any of the three databases (BizTalk Messaging Management, Tracking, or Shared Queue) is lost, or if those databases are otherwise inaccessible. This may occur when you shut down or pause Microsoft SQL Server from Enterprise Manager or if you fail over a clustered database that houses the tables that the BizTalk Messaging Service requires.

BizTalk Server 2000 Service Pack 2 (SP2) modifies the BizTalk Server Interchange application so that when you fail over a clustered BizTalk Server database, you do not have to manually stop and restart the BizTalk Server Interchange application.

Keywords: kbbug kbfix kbbiztalk2000sp2fix KB317083