FIX: Receive locations are disabled in BizTalk Server 2004 when you fail over the MessageBox database (BizTalkMsgBoxDB) (871198)
The information in this article applies to:
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Partner Edition
- Microsoft BizTalk Server 2004 Standard Edition
SYMPTOMSIn Microsoft BizTalk Server 2004, when the MessageBox
database (BizTalkMsgBoxDB) fails over, the receive locations are disabled and
the following warning message is logged in the application event log:Warning:Sending warning to eventlog: '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 enableNote The word "enable" in this error message should be "enabled" and
the sentence should end with a period (".").RESOLUTIONService pack information To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 888751 How to obtain the latest BizTalk Server 2004 service pack Hotfix information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
---------------------------------------------------------
24-Jun-2004 22:23 3.0.5316.0 1,020,928 Btsmsgcore.dll
Note Because of file dependencies, the most recent hotfix that
contains these files may also contain additional files. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in BizTalk Server 2004 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 5/17/2006 |
---|
Keywords: | kbbiztalk2004-2006swept kbBizTalk2004sp1fix kbQFE kbfix kbbug KB871198 kbAudDeveloper |
---|
|