Microsoft KB Archive/870656

= FIX: The Notification Services components remain in the Enable Pending status on a Windows cluster =

Article ID: 870656

Article Last Modified on 4/4/2007

-

APPLIES TO


 * Microsoft SQL Server Notification Services 2.0 Service Pack 1

-



Bug #: 549959 (SQL Server 9.0)



SYMPTOMS
After you install Microsoft SQL Server 2000 Notification Services on a Microsoft Windows cluster, the Notification Services components, such as event providers, generators, and Distributors, remain in the Enable Pending status. However, in Cluster Administrator, the status of the Generic Service cluster resource for Notification Services may be Online.

If you initiate a failover of the generic service for Notification Services in Cluster Administrator, the generic service may start successfully on the other node. However, the Notification Services components may still be in the Enable Pending status. Additionally, there may not be any error messages logged by Notification Services in the event log. This problem may cause both cluster nodes not to process any notification batches.



CAUSE
This problem occurs because of a mismatch between the local computer name and the system name. The system name is the name of the computer that is used by the Notification Services logical components that are provided in the Application Definition File (ADF). When Notification Services starts, Notification Services compares the local computer name to the system name for each logical component. If the local computer name matches the system name of the logical component, the logical component is changed from the Enable Pending status to the Enabled status. If the local computer name does not match the system name of the logical component, the logical component status is not updated to Enabled. When Notification Services is running on a Windows cluster, Notification Services always resolves the local computer name to be the same as the Windows cluster name. Therefore, only logical components that have system names that match the Windows cluster name are assigned the Enabled status.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 Notification Services service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version     Size       File name 30-Jun-2004 16:33  2.0.3008.2  2,101,248  Microsoft.sqlserver.notificationservices.dll 30-Jun-2004 16:33  2.0.3008.2     36,864  Nscontrol.exe



WORKAROUND
To work around this problem, the system name of the logical components that run on the Windows cluster must match the Windows cluster name. You must first make sure that the system name matches the Windows cluster name, and then run the NSControl Update command to synchronize any changes in the Notification Services instance and the application databases.

For more information about the NSControl Update command, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/aa226889(SQL.80).aspx



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
Assume that you are working with a two-node Windows cluster that has the following configuration:
 * Node 1 of the Windows cluster is named NS1.
 * Node 2 of the Windows cluster is named NS2.
 * The Windows cluster name is NSCluster.
 * The virtual SQL Server name is SQLCluster.
 * All the Notification Services logical components are configured to run on the cluster.
 * The system name for all the logical components in the ADF is set to a parameter that is named NSHost.

When the NSHost parameter is set to NSCluster, the configuration is successful because NSHost is set to match the Windows cluster name NSCluster. When the NSHost parameter is set to NS1, the configuration is not successful because NSHost points to the physical node name of Node 1, NS1. Notification Services resolves the local computer name to NSCluster. When the NSHost parameter is set to SQLCluster, the configuration is not successful because NSHost points to the virtual SQL Server name. Notification Services resolves the local computer name to NSCluster.

After you apply this hotfix
After you apply this hotfix, Notification Services uses the Use Network Name for computer name setting to determine the system name for the Notification Services components. You specify the Use Network Name for computer name setting when you create or configure the Generic Service cluster resource by using Cluster Administrator. If you clicked to select the Use Network Name for computer name check box, Notification Services resolves the system name for all the Notification Services components to the value of the Network Name cluster resource on which the Generic Service cluster resource for Notification Services depends.

Note For the Use Network Name for computer name setting to be available when you create the Generic Service cluster resource for Notification Services, you must make sure that the following conditions are true:
 * The Generic Service cluster resource for Notification Services must be created in a cluster group that contains a Network Name cluster resource.
 * The Generic Service cluster resource for Notification Services must depend on the Network Name cluster resource.

Additional query words: NS state

Keywords: kbconfig kbclustering kbfix kbqfe kbhotfixserver KB870656

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.