Article ID: 904168 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
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:
(https://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows registry
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:
Additionally, a Warning event that is similar to the following may be logged in Event Viewer:
[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
Event Type: Warning
This problem occurs after you use the Configframework /s command to reconfigure BizTalk Server 2004 several times.
This problem occurs because of a bug in the Enterprise Single Sign-On component of BizTalk Server 2004.
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must have BizTalk Server 2004 Service Pack 1 (SP1) installed on the computer.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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:
(https://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 904168 - Last Review: January 17, 2015 - Revision: 2.0