FIX: SQL scheme is not updated when you install a hotfix that updates the BizTalk Server databases if a BizTalk Server group is renamed

Article translations Article translations
Article ID: 2505632 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • 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.

CAUSE

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:
HKEY_LOCAL_MACHINE\Software\Microsoft\BizTalk Server\3.0\Administration
For an x64-based computer:
  • HKEY_LOCAL_MACHINE\Software\Microsoft\BizTalk Server\3.0\Administration
  • HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\BizTalk Server\3.0\Administration
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.

RESOLUTION

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.

WORKAROUND

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:
    BizTalk Group
  • Update the value of the BizTalkGroupName registry entry to the new group name manually. To do this, follow these steps:
    1. 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.
    2. Locate and then click the following registry subkey on an x86-based computer:
      HKEY_LOCAL_MACHINE\Software\Microsoft\BizTalk Server\3.0\Administration

      For an x64-based computer, click the following registry subkeys:
      • HKEY_LOCAL_MACHINE\Software\Microsoft\BizTalk Server\3.0\Administration
      • HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\BizTalk Server\3.0\Administration
    3. Right-click BizTalkGroupName, and then click Modify.
    4. In the Value data box, type the new group name, and then click OK.
    5. Exit Registry Editor.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

REFERENCES

For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information about BizTalk Server hotfixes

Properties

Article ID: 2505632 - Last Review: March 18, 2011 - Revision: 1.0
APPLIES TO
  • Microsoft BizTalk Server Branch 2010
  • Microsoft BizTalk Server Developer 2010
  • Microsoft BizTalk Server Enterprise 2010
  • Microsoft BizTalk Server Standard 2010
  • Microsoft BizTalk Server 2009 Branch
  • Microsoft BizTalk Server 2009 Developer
  • Microsoft BizTalk Server 2009 Enterprise
  • Microsoft BizTalk Server 2009 Standard
  • Microsoft BizTalk Server 2006 Developer Edition
  • Microsoft BizTalk Server 2006 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Branch Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2006 Standard Edition
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew kbbiztalk2009presp1fix KB2505632

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com