The generator quantum processed performance counter could not be updated.

Details
Product: SQL Server Notification Services
Event ID: 4095
Source: NotificationServices
Version: 2.0.9999.9
Message: The generator quantum processed performance counter could not be updated.
   
Explanation
Notification Services could not update the Quanta Processed performance counter. Notification Services will attempt to update the counter at the next quantum interval.

If this error occurs several times, it is likely that the Notification Services performance counters are corrupt and will not be updated until the corruption is resolved. There are several possible reasons for the corruption, including a corrupt entry in the registry and problems in other performance monitor DLLs.

   
User Action
If you do not need the Windows Performance counters to be updated, you can safely ignore this warning. For the recommended user action and additional information, see http://support.microsoft.com?kbid=827963.

Related:

The assembly does not contain the required content formatter class.

Details
Product: SQL Server Notification Services
Event ID: 6005
Source: NotificationServices
Version: 2.0.9999.9
Message: The assembly does not contain the required content formatter class.
   
Explanation
This error occurs when the distributor is not able to locate the specified custom content formatter class in the specified assembly or when the assembly is built using a different version of the .NET Framework than is used by Notification Services.
   
User Action
In the ADF, check the <ContentFormatter> element in your notification class definition to ensure that the class name and assembly name for your custom content formatter are correct.

The class name is case sensitive, and must be fully qualified with any namespace prefix. For example, if your formatter class is called MyFormatter and is defined in the MyApplication.CustomComponents namespace, give the class name as MyApplication.CustomComponents.MyFormatter. The assembly name must be specified as a full path. For example, if the assembly containing your formatter is called formatters.dll and is located in C:\bin\CustomComponents, you must specify the assembly name as C:\bin\CustomComponents\formatters.dll.

When possible, build custom components with version 1.0.3705 of the .NET Framework. If you must build custom components with version 1.1.4322 of the .NET Framework, you can force Notification Services to use the same version. To do this, add a <startup> node to the NSService.exe.config file, which is in the vN.N.N.N\Bin folder of Notification Services. The following example shows the <startup> node:

<?xml version=”1.0″ encoding=”UTF-8″?>
<configuration>
<startup>
<supportedRuntime version=”v1.1.4322″/>
<supportedRuntime version=”v1.0.3705″/>
</startup>

The <supportedRuntime> elements restrict the versions of the .NET Framework that Notification Services can use. The order of the listed versions determines the order in which Notification Services attempts to load the .NET Framework versions. In the example above, Notification Services will first attempt to load version 1.1.4322 of the .NET Framework. If it is not available, Notification Services will attempt to load version 1.0.3705 of the .NET Framework.

You must restart the instance of Notification Services to apply changes made to NSService.exe.config.

Related:

Notification Services is terminating the event provider because it returned an error from its Run method.

Details
Product: SQL Server Notification Services
Event ID: 2016
Source: NotificationServices
Version: 2.0.9999.9
Message: Notification Services is terminating the event provider because it returned an error from its Run method.
   
Explanation
This error occurs when an event provider returns false from its Run() method. Both scheduled and continuous event providers get their Terminate() method called by Notification Services if they return false from their Run() methods.

Because Notification Services has no context or additional information about the cause of the failure, the body of this event log entry does not provide additional information.

   
User Action
If an event provider throws an exception from its Run() method to indicate a fatal error, Notification Services includes the description of this exception in the event log entry indicating that the provider’s Run() method has failed. If possible, rewrite the event provider to throw an exception with an informative description of the problem when such a falure occurs. Otherwise, look for information in the event provider’s source code or documentation about the circumstances under which the event provider returns false from its Run() method.

Related:

Notification Services failed to instantiate the event provider.

Details
Product: SQL Server Notification Services
Event ID: 2009
Source: NotificationServices
Version: 2.0.9999.9
Message: Notification Services failed to instantiate the event provider.
   
Explanation
Notification Services could not create an instance of the event provider. This error can occur if a custom event provider was not built using version 1.0.3705 of the .NET Framework. When Notification Services and a custom component use different versions of the .NET Framework, differences in the class libraries can cause application errors.
   
User Action
When possible, build custom components with version 1.0.3705 of the .NET Framework. If you must build custom components with version 1.1.4322 of the .NET Framework, you can force Notification Services to use the same version. To do this, add a <startup> node to the NSService.exe.config file, which is in the vN.N.N.N\Bin folder of Notification Services. The following example shows the <startup> node:
<?xml version=”1.0″ encoding=”UTF-8″?>
<configuration>
<startup>
<supportedRuntime version=”v1.1.4322″/>
<supportedRuntime version=”v1.0.3705″/>
</startup>

The <supportedRuntime> elements restrict the versions of the .NET Framework that Notification Services can use. The order of the listed versions determines the order in which Notification Services attempts to load the .NET Framework versions. In the example above, Notification Services will first attempt to load version 1.1.4322 of the .NET Framework. If it is not available, Notification Services will attempt to load version 1.0.3705 of the .NET Framework.

You must restart the instance of Notification Services to apply changes made to NSService.exe.config.

Related: