You may receive a "Failed to load configuration data for feature: Runtime" error message when you run the Configuration Wizard for BizTalk Accelerator for RosettaNet 3.0 (905729)



The information in this article applies to:

  • Microsoft BizTalk Accelerator for RosettaNet 3.0 Standard Edition
  • Microsoft BizTalk Accelerator for RosettaNet 3.0 Enterprise Edition

SYMPTOMS

When you run the Configuration Wizard for the Microsoft BizTalk Accelerator for RosettaNet 3.0 adapter, you may receive an error message that is similar to the following:
Failed to load configuration data for feature: Runtime. Please see the log file for more details.

CAUSE

This issue occurs if the in-process host and the isolated host are configured to use the same Microsoft Windows group.

RESOLUTION

To resolve this issue, configure the in-process host and the isolated host to use different Windows groups. To do this, follow these steps:
  1. Verify that the following Windows groups exist, and that the appropriate users are members of each group:
    • A group that is named BizTalk Application Users for the in-process host.
    • A group that is named BizTalk Isolated Host Users for the isolated host.
  2. Start the BizTalk Administration console.
  3. Expand the computer that you want that is running Microsoft BizTalk Server 2004, and then expand Hosts.
  4. Right-click BizTalkServerApplication, and then click Properties.
  5. In the Windows Group box, type BizTalk Application Users, and then click OK.
  6. Right-click BizTalkServerIsolatedHost, and then click Properties.
  7. In the Windows Group box, type BizTalk Isolated Host Users, and then click OK.
  8. Close the BizTalk Administration console.

MORE INFORMATION

This issue occurs when the BizTalk Accelerator for RosettaNet 3.0 Configuration Wizard tries to configure permissions for the in-process host and for the isolated host to the BizTalk databases that are stored in Microsoft SQL Server. When both hosts use the same Windows group, the Configuration Wizard tries to grant access to the BizTalk databases two times for the same group. Therefore, the configuration fails.

When you experience this issue, you may see entries that are similar to the following in the configuration log.

Note In these entries, name is the name of the computer or domain, and path is a file path.[8:39:37 PM Info ConfigHelper] name\IA_BizTalk_Application_Users is not a local entity.
[8:39:37 PM Info RNConfig] Entering function: CRNConfig::GrantLogin
[8:39:37 PM Info ConfigHelper] Executed SQL statement on database: BTARNCONFIG on computer: testcomp
[8:39:37 PM Error ConfigHelper] The group 'BizTalk_Application_Users' already exists in the current database.
[8:39:37 PM Error ConfigHelper] SQL error: 42000 Native error code: 15024
[8:39:37 PM Error ConfigHelper]
path\common\configwizard\confighelper\sqlhelper.cpp(1444): FAILED hr = 80040e14

[8:39:37 PM Error ConfigHelper]
path\common\configwizard\confighelper\sqlhelper.cpp(1652): FAILED hr = 80040e14

[8:39:37 PM Error ConfigHelper]
path\common\configwizard\confighelper\sqlhelper.cpp(1063): FAILED hr = 80040e14

[8:39:37 PM Error ConfigHelper]
path\common\configwizard\confighelper\sqlhelper.cpp(439): FAILED hr = 80040e14

[8:39:37 PM Error ConfigHelper] Failed to execute SQL statement on database: BTARNCONFIG on computer: testcomp
[8:39:37 PM Error ConfigHelper] The group 'BizTalk_Application_Users' already exists in the current database.
[8:39:37 PM Error RNConfig]
path\btarnconfig\dll\rnconfig.cpp(3588): FAILED hr = 80040e14

[8:39:37 PM Info RNConfig] Leaving function: CRNConfig::GrantLogin
[8:39:37 PM Error RNConfig]
path\btarnconfig\dll\rnconfig.cpp(1738): FAILED hr = 80040e14

[8:39:37 PM Info RNConfig] Leaving function: CRNConfig::ConfigureFeature
[8:39:37 PM Info ConfigFramework] Waiting for configuration thread to complete.
[8:39:39 PM Info ConfigFramework] Showing MessageBox with text: An error occurred configuring feature: Runtime Return Code: 2
[8:39:39 PM Error ConfigFramework]
path\common\configwizard\exe\configthread.cpp(556): FAILED hr = 80040e14

REFERENCES

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

816302 How to manage groups in Windows Server 2003


Modification Type:MajorLast Reviewed:10/6/2005
Keywords:kbtshoot kbprb KB905729 kbAudDeveloper kbAudITPRO