Microsoft Knowledge Base Email Alertz

(840705) - Describes a workaround for a configuration failure of Microsoft BizTalk Server 2004 on a Microsoft Windows XP-based computer.

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: 840705 - Last Review: October 31, 2006 - Revision: 1.4

You receive a “Failed to generate the master secret (error code 0X80070005)” error message when you configure BizTalk Server 2004 on a Windows XP-based computer

On This Page

SYMPTOMS

When you configure Microsoft BizTalk Server 2004 on a Microsoft Windows XP-based computer, you may receive the following error message:
Failed to generate the master secret (error code 0X80070005).
The following error message may also be logged in the Config log that is in the Temp folder:
Failed to generate the master secret (error code 0X80070005). Return code number

CAUSE

This issue may occur if one of the following conditions is true:
  • The computer name is not recognized and is not mapped to the IP address. This condition exists if the return code that is displayed in the Config log file is 2.
  • The computer is a member of the workgroup. This issue may occur if the return code that is displayed in the Config log file is 4. By default, the following registry key is enabled. A DWORD value of 1 indicates the registry key is enabled.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\ForceGuest

Therefore, the Security Support Provider Interface (SSPI) tries to log on by using the guest user account and fails.

WORKAROUND

To work around this issue, determine the return code in the Config log file, and then follow the steps that are appropriate for your situation.

The return code in the Config log file is 2

Use one of the following methods.

Method 1

Map the computer name to the IP address in the Hosts file. You can use Notepad to change the Hosts file. The Hosts file is in the following location:
Windows Folder\System32\Drivers\Etc

Method 2

Remove the computer from the domain.

The return code in the Config log file is 4

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  (http://kbalertz.com/Feedback.aspx?kbNumber=322756/ ) How to back up and restore the registry in Windows


Set the forceguest value in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
subkey to 0 (zero). To do this, follow these steps.
  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. In Registry Editor, locate the
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    subkey, right-click forceguest, click Modify, type 0, and then click OK.
  3. Quit Registry Editor.

MORE INFORMATION

The following table indicates how the Security Support Provider Interface (SSPI) tries to log on according to the settings in the registry.
Collapse this tableExpand this table
Registry valueValueStatusResult
Forceguest1EnabledThe SSPI logs on by using the guest user account.
Forceguest0DisabledThe SSPI logs on as the user who is specified.
If the guest account is enabled, the SSPI can log on successfully by using the guest account and any user credentials.

If the guest account is disabled, the SSPI logon fails regardless of whether you provide valid credentials. This is the default behavior in Windows XP in a peer-to-peer network.

REFERENCES

For additional information about this issue, click the following article numbers to view the articles in the Microsoft Knowledge Base:
827918  (http://kbalertz.com/Feedback.aspx?kbNumber=827918/ ) Cannot install Commerce Server 2002 Developer Edition on Windows XP.
294355  (http://kbalertz.com/Feedback.aspx?kbNumber=294355/ ) Netdom.exe cannot join a Windows XP Professional-based computer to a domain
290403  (http://kbalertz.com/Feedback.aspx?kbNumber=290403/ ) How to set security in Windows XP Professional that is installed in a workgroup

APPLIES TO
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Standard Edition, when used with:
    • the operating system: Microsoft Windows XP
Keywords: 
kbbts kbbiztalk2004-2006swept kbtshoot kbsetup kbprb KB840705
       

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

Anonymous User Report As Irrelevant  
Written: 4/6/2005 7:24 AM
If you are XP SP2 then the issue is more likely to be the changes to RPC. See - http://support.microsoft.com/default.aspx?scid=kb;en-us;841893 Quinkin