FIX: An "Enterprise Single Sign-On is offline" error message may be logged in the Configuration log when you try to use the "Configframework /s" command to silently reconfigure BizTalk Server 2004 (904168)

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

You try to use the Configframework /s command together with the Configxml.xml file to silently reconfigure Microsoft BizTalk Server 2004. When you do this, an error message that is similar to the following may be logged in the Configuration log:

[13:37:30 Error BtsCfg] Creation of Adapter FILE Configuration Store entries failed.
Enterprise Single Sign-On is offline.
[13:37:30 Error BtsCfg] path\btscfg\btscfg.cpp(886): FAILED hr = c0002a10
[13:37:30 Info BtsCfg] Leaving function: CBtsCfg::ConfigureFeature
[13:37:30 Info ConfigFramework] Showing MessageBox with text: Creation of Adapter FILE Configuration Store entries failed.
Enterprise Single Sign-On is offline. Return Code: 2

Additionally, a Warning event that is similar to the following may be logged in Event Viewer: Event Type: Warning
Event Source: ENTSSO
Event Category: Enterprise Single Sign-On
Event ID: 10536
Description: SSO AUDIT Function: ControlApplication Tracking ID: ba8b0897-9929-4df2-8519-706e4b041f6e Client Computer: computername (wmiprvse.exe:316) Client User: - Application Name: {0DA0E9C9-FD61-42CA-8D40-5DE8FEE02143} Error Code: 0xC0002A10, Enterprise Single Sign-On is offline. Note In this Warning event, computername is a placeholder for the name of the computer.

This problem occurs after you use the Configframework /s command to reconfigure BizTalk Server 2004 several times.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next BizTalk Server 2004 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To apply this hotfix, you must have BizTalk Server 2004 Service Pack 1 (SP1) installed on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version     Size    File name
   -----------------------------------------------------
   07-Jul-2005  17:00  3.0.6140.0  66,560  Infocache.dll

MORE INFORMATION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

After you apply this hotfix, you must add the WaitForOnline entry to the registry to resolve this problem. To add the WaitForOnline entry to the registry, follow these steps:

Click Start, click Run, type Regedit, and then click OK.
Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\ENTSSO
Right-click ENTSSO, point to New, and then click DWORD Value.
Type WaitForOnline, and then press ENTER.
Right-click WaitForOnline, and then click Modify.
In the Value data box, type 1, and then click OK.
Quit Registry Editor.

For more information about the terminology that Microsoft uses when Microsoft corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates