Article ID: 2505632 - View products that this article applies to.
Consider the following scenario:
<Date Time> Logon Login failed for user '<user account>'. Reason: Failed to open the explicitly specified database. [CLIENT: <IP address>]
<Date Time> Logon Error: 18456, Severity: 14, State: 38.
For example, you rename a BizTalk Server group before you apply the cumulative update package 1 for BizTalk Server 2009 that includes the Biztalkmsgboxdbsps.sql script. After the update is applied, the BizTalkMsgBoxDb database is not updated.
Note This issue also occurs in Microsoft BizTalk Server 2006, Microsoft BizTalk Server 2006 R2, and Microsoft BizTalk Server 2010.
This issue occurs because the Name value of the BizTalk Server group does not match the value of the BizTalkGroupName registry entry in the registry subkeys for the operating system:
For an x86-based computer:
For an x64-based computer:
When the BizTalk Server group is renamed, the Name value of the BizTalk Server group is updated to the new group name. However, the value of the BizTalkGroupName registry entry is not updated. Therefore, the error message that is mentioned in the "Symptoms" section is logged.
Cumulative update informationThe hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2009.
For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2497794Note The hotfixes for Microsoft BizTalk Server 2006, for Microsoft BizTalk Server 2006 R2, and for Microsoft BizTalk Server 2010 are currently not available. To work around this issue, see the "Workaround" section.
(https://support.microsoft.com/kb/2497794/ )Cumulative update package 2 for BizTalk Server 2009
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756To work around this issue in BizTalk Server 2006, in BizTalk Server 2006 R2, in BizTalk Server 2009, and in BizTalk Server 2010, use one of the following methods before you install the update:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/2003907/ )Information about BizTalk Server hotfixes
Article ID: 2505632 - Last Review: March 18, 2011 - Revision: 1.0