Rediger

Del via


Behavior of BizTalk Server Host Instances during SQL Server Failover

BizTalk Server databases housed on a clustered instance of Microsoft SQL Server are temporarily unavailable if the clustered instance of SQL Server experiences a failover. This section documents the behavior of the host instances associated with BizTalk Server when the BizTalk Server databases are unavailable.

Behavior of In-Process Host Instances during SQL Server Failover

If the BizTalk Server databases are unavailable, then an in-process instance of a BizTalk Server host will be recycled until the connection to the SQL Server is restored. Once the connection to the SQL Server databases is restored, document processing resumes normally.

Behavior of Isolated Host Instances During SQL Server Failover

If the BizTalk Server databases are unavailable, then an isolated instance of a BizTalk Server host will pause and an error similar to the following will be generated in the BizTalk Server Application log:

All receive locations are being temporarily disabled because either   
the MessageBox or Configuration database is not available.   
When these databases become available, the receive locations will be automatically enabled.  

Once the connection to the SQL Server databases is restored an informational message similar to the following is written to the BizTalk Server Application log and document processing resumes normally:

All receive locations are being enabled because both the MessageBox and Configuration databases are back online.  

See Also

Hosts