The information in this article applies to:
BUG #: 55368 (SQLBUG_70) SYMPTOMSWhen replication is set up on an active/passive cluster and the SQL server instance fails over from the primary node of the cluster to the secondary node, replication distribution tasks running on the failover node (secondary node) of the cluster might fail with an error message:
CAUSEIf an active/passive cluster is set up, SQL server is installed only on the primary node of the cluster. Therefore, the license information is local to the primary node and, when failover takes place, the secondary node, which does not have license information for SQL server 7.0, cannot validate the replication scenario and see whether "per seat" or "per server" license mode is set. WORKAROUNDIn order to overcome this problem, the registry replication feature in the NT clustering can be used as follows:
SYSTEM\CurrentControlSet\Services\LicenseInfo\MSSQL7.00 Failover the SQL group on the cluster administrator to secondary node and note that the registry changes should be propagated to the secondary node. STATUSMicrosoft has confirmed this to be a problem in SQL Server version 7.0. MORE INFORMATIONIn an active/active cluster setup for replication/DTS to work between Enterprise and desktop/MSDE edition in case of failover, both nodes of the cluster should have SQL server 7.0 set to "per seat" licensing mode. This needs to occur even though replicating LicenseInfo registry key between the nodes is not required because licensing info is already available on the second node of the cluster by virtue of active/active setup. Additional query words:
Keywords : kbSQLServ kbSQLServ700 kbSQLServ700bug |
Last Reviewed: October 4, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |