Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

BUG: SQL Server Setup Causes Assertion Failures When BizTalk Server Is Installed on Cluster


View products that this article applies to.

This article was previously published under Q293352

↑ Back to the top


Symptoms

When you install Microsoft SQL Server 2000 on a Microsoft Windows 2000 clustered computer that already has BizTalk Server 2000 installed, you may receive the following error:
Microsoft Visual C++ Debug Library
Debug Assertion Failed!

Program: D:\WINNT\TEMP\_ISTMP1.DIR\_INS5576._MP
File: d:\bts\private\cis\common\sku\setupex\setupex.c
Line: 127

↑ Back to the top


Cause

When you run the SQL Server Setup program on a clustered computer that already has BizTalk Server installed, two dialog boxes display assertion failures from BizTalk Server. The assertion failures occur because the SQL Server Setup program uses a DLL named Setupex.dll, which is also included in BizTalk Server. Because of this DLL naming conflict, SQL Server Setup incorrectly loads the BizTalk Server version of Setupex.dll, which causes the assertion failures.

↑ Back to the top


Resolution

Install SQL Server before you install BizTalk Server 2000. If this is not possible, rename the BizTalk Server version of Setupex.dll file before you run SQL Server Setup. To do this, perform the following steps:
  1. Open the Program Files\Microsoft BizTalk Server folder where BizTalk Server is installed.
  2. Rename the Setupex.dll file as Bts_setupex.dll.
  3. Run the SQL Server Setup program.
When the SQL Server Setup is complete, change the name of the BizTalk Server version of the Setupex.dll file back to its original name:
  1. Open the Program Files\Microsoft BizTalk Server folder where BizTalk Server is installed.
  2. Change the Bts_setupex.dll file to Setupex.dll.

↑ Back to the top


Status

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

↑ Back to the top


Keywords: KB293352, kbbug

↑ Back to the top

Article Info
Article ID : 293352
Revision : 4
Created on : 10/22/2003
Published on : 10/22/2003
Exists online : False
Views : 374