Microsoft KB Archive/297594

= BUG: BizTalk Server Setup Fails to Connect the Second Instance (Named Instance) of SQL Server =

Article ID: 297594

Article Last Modified on 9/30/2003

-

APPLIES TO


 * Microsoft BizTalk Server 2000 Standard Edition

-



This article was previously published under Q297594



SYMPTOMS
When you run the BizTalk Server 2000 Setup program, the Configure BizTalk Database dialog box prompts you for a SQL Server name. If SQL Server is installed on a remote computer and there are two instances of the SQL Server running, you must specify the instance by typing the remote server name and the instance name, separated by a backslash ( \ ). When you specify the server name and instance, and then click Continue, the following error occurs:

An error occurred while attempting to create the BizTalk Messaging Management database.

The specified SQL server might not be running or the server name might be incorrect.

Hresult:0x80004005

Description: Client unable to establish connection (2 error/s)

Source: Microsoft OLE DB Provider for SQL Server



CAUSE
The BizTalk Messaging Management database administrative objects do not work with the Named Pipes protocol for a second instance of SQL Server 2000. Therefore, TCP/IP is required.



RESOLUTION
Run SQL Server setup on the BizTalk Server computer and select Connectivity Only during the installation. After the SQL Server components are installed, complete the following steps:


 * 1) Click Start, point to Programs, click Microsoft SQL Server, and then click Client Network Utility. The SQL Server Client Network Utility console appears.In the Enabled protocols by order list, select TCP/IP the first protocol.In the properties for the TCP\IP protocol, change the default port to the port for the second SQL Server instance.Run the BizTalk Server Setup program.
 * 2) In the Enabled protocols by order list, select TCP/IP the first protocol.In the properties for the TCP\IP protocol, change the default port to the port for the second SQL Server instance.Run the BizTalk Server Setup program.
 * 3) In the properties for the TCP\IP protocol, change the default port to the port for the second SQL Server instance.Run the BizTalk Server Setup program.
 * 4) Run the BizTalk Server Setup program.



STATUS
Microsoft has confirmed that this is a problem in BizTalk Server 2000.

Keywords: kbbug kbfix KB297594

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.