Symptoms
Consider the following scenario:
-
You have a BizTalk group that includes two BizTalk Server 2013 R2 servers.
-
You have Microsoft BizTalk Server 2013 R2 Accelerator for RosettaNet (BTARN) configured on one of the BizTalk servers.
-
You try to configure BTARN on the other BizTalk server by using the Join option to join the group.
In this scenario, the configuration process fails on the second BizTalk server, and you receive the following error message:
[<DateTime> Error ConfigHelper] [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.[<DateTime> Error ConfigHelper] SQL error: 08001 Native error code: 17[<DateTime> Error ConfigHelper] d:\<Path>\configwizard\confighelper\sqlhelper.cpp(1235): FAILED hr = 80004005[<DateTime> Error ConfigHelper] d:\<Path>\configwizard\confighelper\sqlhelper.cpp(720): FAILED hr = 80004005[<DateTime> Error ConfigHelper] Failed to execute SQL statement on database: master on computer: [<DateTime> Error ConfigHelper] [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.[<DateTime> Warning Configuration Framework]Exception XML: <Exception Message="Unexpected exception occurred while configuring [Runtime]." Source="<Source>" HelpID="<HelpID>"><Exception Message="Attempted to read or write protected memory. This is often an indication that other memory is corrupt." Source="<Source>" HelpID="<HelpID>" /></Exception>[<DateTime> Info Configuration Framework]Configuration Summaries:[<DateTime> Error Configuration Framework]Feature: [Runtime] Failed to configure with error message [<Exception Message="Unexpected exception occurred while configuring [Runtime]." Source="<Source>" HelpID="<HelpID>"><Exception Message="Attempted to read or write protected memory. This is often an indication that other memory is corrupt." Source="<Source>" HelpID="<HelpID>" /></Exception>]
Cause
The issue occurs because of a code defect in the Microsoft BizTalk 2013 R2 Accelerator for RosettaNet Configuration Wizard.
Resolution
Cumulative update information
This issue was first fixed in the following cumulative update of BizTalk Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For information about the service packs and the cumulative update list for BizTalk Server, see KB 2555976: Service pack and cumulative update list for BizTalk Server.For more information about BizTalk Server hotfixes, see KB 2003907: Information about BizTalk hotfixes and Service Pack support.
