Microsoft KB Archive/274227

{|
 * width="100%"|

LDAP Fails to Connect to SQL Server When You Change the SQL Server Default Communication TCP Port

 * }

Q274227

-

The information in this article applies to:


 * Microsoft Site Server version 3.0

-

SYMPTOMS
When you change the SQL Server TCP port address from the default 1433 to something else, the Site Server Membership Instance fails to connect to SQL Server.

CAUSE
The Site Server Membership database relies on the SQL Server name specified in the DSOGRID table of the Membership database in order to communicate. If the SQL Server name changes or the port number changes after the Membership database has been created, then these changes need to be reflected in the DSOGRID table.

RESOLUTION
The following example illustrates the changes that need to be made in the SQL Server DSOGRID table, and the changes that are required in the LDAP instance properties.

Example
Assume that your SQL Server computer is named SQLSRV01, and the TCP server listening port has been changed to 1653, then the following changes need to be made:

  On the computer running Site Server, change the properties for the LDAP instance that is connecting to SQL Server so that the SQL Server computer name on the Root Database tab is specified as follows: "SQLSRV01,1653" In Control Panel Services, stop the Site Server LDAP Service.  Update the DsoGrid table in your Membership database to reflect the correct vc_datasource name by running the following script: Use SS3MemDB

GO

update dsogrid

SET vc_Datasource = &quot;SQLSRV01,1653&quot;  Restart the LDAP instance.

MORE INFORMATION
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

"Q229044 Err Msg: SAWIZARD The New Membership Server Wizard Has Failed..." Additional query words:

Keywords :

Issue type : kbprb

Technology :