BUG: Commerce Server Cannot Connect to a Clustered Named Instance Through a Firewall (810322)


The information in this article applies to:

  • Microsoft Commerce Server 2002
  • Microsoft SQL Server 2000 Enterprise Edition

SYMPTOMS

After you install Commerce Server, you may not be able to view Commerce Server parameters in the Microsoft Management Console (MMC). When you right-click Commerce Server Manager, click Properties, click Modify, and then click Test Connection, you may receive the following error message:
Test connection failed because of an error in initializing provider. [DBNETLIB][ConnectionOpen (connect()).]Specified SQL Server not found .
This error occurs when you try to connect to a clustered named instance of SQL Server through a firewall

CAUSE

When Commerce Server connects to a computer that is running a virtual instance of SQL Server, and if Network Address does not specify the destination TCP port, the client library queries the server on port UDP 1434 to collect information about the instance.

When the server returns the information, the network frame contains the IP address of the physical node instead of the IP address of the virtual server. Depending on the firewall configuration, this network packet may be dropped, and the client may not receive any answer.

RESOLUTION

You must specify the listening port of the named instance in the Commerce Server connection string. By default, the SQL named instance listens on port 1434.

To resolve this problem, follow these steps:
  1. Find the listening port number of the SQL named instance.
    1. Open SQL Enterprise Manager.
    2. Right-click the appropriate instance in the SQL Server Group.
    3. Click Properties.
    4. In the SQL Server Properties dialog box, click the General tab, and then click Network Configuration. This opens the SQL Server Network Utility dialog box.
    5. Select TCP/IP, and then click Properties.
    6. The default port number appears in the text box.
  2. Add the port number and the virtual IP address of your SQL Server in the Commerce connection string.
    1. Open Commerce Server Manager.
    2. Right-click Commerce Server Manager.
    3. Click Properties.
    4. In the Commerce Server Manager Properties dialog box, click Modify. This opens the Data Link Properties dialog box.
    5. Click the All tab.
    6. Select Network Address, and then click Edit Value.
    7. Type the virtual IP address of the virtual instance of SQL Server and the port number, separated by a comma. For example, if the virtual IP address of SQL Server is xxx.xxx.xx.x, and it is listening on TCP/IP port number 2433, type the following for Network Address:

      xxx.xxx.xx.x,2433

STATUS

Microsoft has confirmed that this is a bug in Microsoft SQL Server 2000.

REFERENCES

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

318432 BUG: Cannot Connect to a Clustered Named Instance Through a Firewall

Modification Type:MinorLast Reviewed:4/29/2003
Keywords:kbClustering kbBug kberrmsg KB810322 kbAudDeveloper kbAudITPRO
©2002 Microsoft Corporation. All rights reserved.