Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: Failover of a SQL Virtual Server Causes Problems with Active Directory Integration
Article ID: 299362 - View products that this article applies to.
This article was previously published under Q299362
BUG #: 235394 (SHILOH_BUGS)
In SQL Server 2000, an instance of the server along with any publications, databases or other objects it contains may be integrated with Active Directory (AD). The AD integration information for the instance is stored in the following registry keys:
Clustered or Nonclustered Default Instance
Clustered or NonClustered Name Instance
HKLM\Software\Microsoft\Microsoft SQL Server\InstanceName\SQLServerSCP
When you register a virtual SQL Server server with the AD either through the GUI or by using the sp_activedirectory_scp stored procedure, the preceding registry keys are updated with the integration information. When a failover of the SQL Server virtual server occurs, the key is not copied over to the other node.
Because the current node does not have any information about the AD integration of the virtual server, users are not be able to view the database objects, or publications that were registered in the AD.
The SQL Server Active Directory service, MSSQLADHelper, is used for integration of SQL Server and it's objects with the Active Directory. This service, by default, runs under the Local System account and is started as needed when you add new SQL Server objects or you refresh AD information.
Setup fails to create the preceding registry key and during a failover, the registry key is not being replicated to the other node, when then causes AD integration issues.
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/EN-US/ )INF: How to Obtain the Latest SQL Server 2000 Service Pack
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.