This article has been archived. It is offered "as is" and will no longer be updated.
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:
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.
Run the following command to clear the Domain Name System (DNS) cache:
Restart the Windows SharePoint Services 3.0 Timer service.