Microsoft KB Archive/827963

= Resolve Corrupted Notification Services Performance Counters =

Article ID: 827963

Article Last Modified on 5/18/2007

-

APPLIES TO


 * Microsoft SQL Server Notification Services 2.0
 * Microsoft SQL Server Notification Services 2.0 Service Pack 1

-



SYMPTOMS
This article discusses the steps to take when Microsoft SQL Server Notification Services performance counters become corrupted. There are several possible reasons for the corruption, including a corrupt entry in the registry and problems in other performance monitor DLLs. This corruption causes your application event log to fill up with error events that are related to the performance counters. Event ID 9057 errors are most commonly logged, and event IDs 4093, 4098, and 5500-5504 errors also occasionally appear.

The following events may be logged in the application event log:



RESOLUTION
To resolve the corrupted SQL Server Notification Services performance counters, you must reregister the Notification Services service on your computer. To do so, follow these steps:  Open a command prompt. Locate the Bin folder for the Microsoft SQL Server Notification Services service. The typical location of this folder is C:\Program Files\Microsoft SQL Server Notification Services\v2.0.xxxx.x\Bin folder.  Run the following command to stop the SQL Server Notification Services service: net stop NS$   After the SQL Server Notification Services service is successfully stopped, run the following command to unregister the instance of SQL Server Notification Services that is running on your computer: nscontrol unregister -name 

Note You may have to restart your computer before you register the SQL Server Notification Services.   Run the following command to reregister the instance of SQL Server Notification Services: nscontrol register -name  -service 

Note Specify the same command-line arguments that you specified when you originally registered the instance of SQL Server Notification Services. For example, if you use SQL Server security, you must specify the -sqlusername command-line argument and the -sqlpassword command-line argument. For more information, see the &quot;NSControl Register&quot; in SQL Server Notification Services Books Online. </li>  Run the following command to start the SQL Server Notification Services service: net start NS$<Instance_name> </li></ol>

You may have to repeat these steps several times or reboot your computer between running NSControl Unregister and NSControl Register to resolve the problem. If these steps do not stop the entries in the application log, there is a Microsoft .NET Framework fix that might resolve the problem.

If you have the .NET Framework version 1.0 and the .NET Framework version 1.1 installed side-by-side on the affected server, obtain the .NET Framework fix that is detailed in the following article in the Microsoft Knowledge Base:

813350 FIX: &quot;Category Not Found&quot; Error Message When You Run a New Visual Studio .NET Application in a Side-by-Side Environment

After you obtain this fix, follow these steps: <ol>  Use the following command to stop each instance of SQL Server Notification Services: net stop ns$instance_name </li> Apply the .NET Framework fix.</li>  Use the following command to restart each instance of SQL Server Notification Services: net start ns$instance_name </li></ol>

<div class="references_section">