An exception is thrown when you run the SPDatabaseServerDiagnosticsPerformanceCounterProvider class after you set up an SQL aliasing

Article translations Article translations
Article ID: 981230 - View products that this article applies to.
Expand all | Collapse all


Consider the following scenario. You have a server farm on which the Windows SharePoint Services 3.0 Timer service is running. The server farm includes one front-end server and one back-end server. Then, you set up an SQL aliasing for an instance of Microsoft SQL Server.

In this scenario, when you enable the SPDatabaseServerDiagnosticsPerformanceCounterProvider class and then run the class, an exception may be thrown out.


To work around this issue, follow these steps:
  1. Change the host files on the front-end server to resolve the SQL aliasing to the corresponding IP address of the instance of SQL Server.
  2. Run the following command to clear the Domain Name System (DNS) cache:

    ipconfig /flushdns
  3. Restart the Windows SharePoint Services 3.0 Timer service.


Article ID: 981230 - Last Review: September 22, 2011 - Revision: 4.0
  • Microsoft SharePoint Foundation 2010
  • Microsoft SharePoint Server 2010
kbexpertiseinter kbtshoot kbsurveynew kbprb KB981230

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from