You rename a BizTalk Server group on a computer that is running Microsoft BizTalk Server 2009.
You install a hotfix that updates the SQL schema for BizTalk Server 2009 databases.
In this scenario, the SQL schema for BizTalk Server 2009 databases is not updated. Additionally, an error message that resembles the following is logged in the SQL Server error log:
<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:
Note The adm_group table of the BizTalkMgmtDb database contains the Name value of the BizTalk Server group.
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 information
The 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:
2497794 Cumulative update package 2 for BizTalk Server 2009
Note 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.
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:
322756 How to back up and restore the registry in Windows
To 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:
Rename the BizTalk Server group back to the following default BizTalk Server group name:
Update the value of the BizTalkGroupName registry entry to the new group name manually. To do this, follow these steps:
Open Registry Editor. To do this, use the appropriate method for your operating system:
In Windows 2008, Windows 2008 R2, Windows Vista, or Windows 7, click Start, type regedit in the Start Search box, and then press ENTER.
In Windows 2003 or Windows XP, click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey on an x86-based computer: