Event Log Errors Occur on Membership Directory after Upgrading to MDAC 2.1 SP2

• Microsoft Site Server version 3.0

SYMPTOMS

When you upgrade the Microsoft Data Access Components (MDAC) on your Site Server computer, the System log may generate one or more of the following event IDs:

Event ID: 2500
Source: LDAPSVC
Description: The server failed to start due to an initialization error. Verify the configuration. Error description is: GetLastError()=-2146893792: StaticStore.

Event ID: 481
Source: LDAPSVC
Description: Site Server LDAP Service cannot initialize the following object: GetLastError()=-2146893792 : Init LdapExtension.

Event ID: 20
Source: P&M Directory Store
Description: Unable to connect to DB server with the connect string: Driver=(SQL Server);SERVER=<odbc name>;DATABASE=<membership database>;UID=sa;PWD=*****;NETWORK=dbmssocn.dll. Validate login and verify database is running with TCP/IP support.

Event ID: 4107
Source: MembershipBroker
Description: The Site Server Authentication Service could not do an LDAP bind. Error: 81, virtual server number 2. If this happened during a reboot of the machine and the LDAP server is on the same machine, it is not critical. The Authentication Service wil automatically recover from this problem when the first authentication happens.

Event ID: 4102
Source: MembershipBroker
Description: The Site Server Authentication Service could not connect to the LDAP server. Error: 81, virtual server number 2. If this happened during a reboot of the machine and the LDAP server is on the same machine, it is not critical. The Authentication Service wil automatically recover from this problem when the first authentication happens.

CAUSE

This problem occurs when you attempt to connect to the SQL Server computer using a SQL Server alias name and you have Microsoft Data Access Components version 2.1 SP2 installed on your Site Server computer.

RESOLUTION

To resolve this issue, do one of the following:

• Create a new Membership Server Instance using the actual SQL Server name to replace the failing Membership Server Instance.


-or-


• Correct the SQL Server name in the database and the LDAP properties.

Creating a New Membership Server Instance

1. Change the server name that is stored in the Membership database. Using isql/w or Query Analyzer, execute the following script:

   Update DsoGrid
   Set vc_datasource = '<actual SQL server name>'
   Where vc_datasource = '<SQL server alias>' 




2. Create a new instance using the actual SQL Server name instead of the SQL Server alias. For more information, refer to the online documentation that ships with Microsoft Site Server.



3. Re-map your services to the new Membership Server Instance.

Correcting the SQL Server Name

1. Change the server name that is stored in the Membership database. Using isql/w or Query Analyzer, execute the following script:

   Update DsoGrid
   Set vc_datasource = '<actual SQL server name>'
   Where vc_datasource = '<SQL server alias>' 




2. From the MMC, expand the Personalization and Membership object, expand your server, and expand the target membership server instance.



3. Right-click the LDAP object and click Properties.



4. Click OK on the two error dialog boxes.



5. Click the Root Database tab, change the SQL Server name to reflect the actual server name, and then click OK.



6. Click Yes to the confirmation message.



7. Right-click the LDAP object and click Start.

MORE INFORMATION

For additional information, please see the following articles in the Microsoft Knowledge Base:

Q216415 INF: How to Set Up SQL Server for Access Through Proxy Server

Q238648 Database Error when Creating a Membership Directory Using a SQL Server Alias

Additional query words:

Keywords :
Version : winnt:3.0
Platform : winnt
Issue type : kbprb