Microsoft Knowledge Base Email Alertz

How to recover a single-node BizTalk Server 2004 configuration after the Configframework.exe /u command is run accidentally

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 921992 - Last Review: March 16, 2007 - Revision: 1.2

How to recover a single-node BizTalk Server 2004 configuration after the Configframework.exe /u command is run accidentally

On This Page

INTRODUCTION

This article describes how to recover a single-node Microsoft BizTalk Server 2004 configuration after the Configframework.exe /u command is run accidentally.

MORE INFORMATION

To recover a single-node BizTalk Server 2004 configuration after you have run the Configframework.exe /u command, follow these steps.

Notes
  • You must have the Enterprise Single Sign-On (SSO) master secret key backed up. If you do not have the SSO master secret key backed up, you cannot recover from this scenario.
  • You must have BizTalk Server 2004 Enterprise Edition or BizTalk Server 2004 Developer Edition installed to follow these steps. Other editions of BizTalk Server 2004 do not have the option to join a group.
  • This article does not address how to recover from hardware failures that may potentially cause data loss. For more information about how to back up and to restore the BizTalk databases, visit the following Microsoft Web site:
    http://msdn2.microsoft.com/en-us/library/ms962212.aspx (http://msdn2.microsoft.com/en-us/library/ms962212.aspx)
  1. Click Start, click Run, type the path of the Configframework.exe file, and then click OK.

    Note By default, the Configframework.exe file is located in the Program Files\Microsoft BizTalk Server 2004 folder.
  2. Double-click Configframework.exe, and then click Next.
  3. In the Do you want to create or join a BizTalk Server group list, click Join.
  4. In the Will this Single Sign-On server (SSO) hold the master secret key? list, click No.

    Note This step enables you to use the existing BizTalk and SSO databases.
  5. Follow the instructions on the screen to complete the Microsoft BizTalk Server 2004 Configuration Wizard.

    Note The BizTalk and SSO services do not start because there is no master secret server.
  6. Click Start, click Run, type cmd, and then click OK.
  7. At the command prompt, use the CD command to move to the folder where the Ssoconfig.exe file is located.

    Note By default, the Ssoconfig.exe file is located in the Program Files\Common Files\Enterprise Single Sign-On folder.
  8. At the command prompt, type Ssoconfig -restoresecret filename. filename is the name of the file where the master secret key is stored.
  9. Restart the Enterprise Single Sign-On service. In Event Viewer, verify that there are no errors.
  10. Restart the BizTalk Host service. In Event Viewer, verify that there are no errors.

Registry changes

The Configframwork.exe /u command removes all BizTalk Server 2004 services. Therefore, you must manually modify any registry keys that were modified before the Configframework.exe /u command was run accidentally. BizTalk Server registry keys are located under the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc{GUID}
You can install BizTalk Server 2004 Rollup Package 1 or BizTalk Server 2004 Service Pack 1 (SP1) on a BizTalk server that is not configured. Therefore, you do not have to modify any registry changes that are related to BizTalk Server 2004 Rollup Package 1 or to BizTalk Server 2004 SP1.

APPLIES TO
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Developer Edition
Keywords: 
kbbtsframework kbbts kbhowto KB921992
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate