Wednesday, November 19, 2008

aspnet_perf.dll failures in event log

Your log contains this error: (NB. I only partly copied it.. )

ASP.NET_2.0.50727" in DLL "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\aspnet_perf.dll" failed.

The solution:

Download exctrlst.exe from Windows 2000 Resource Kit, and run it.

Disable Counter for any reference to path containing: "v2.0.50727\aspnet_perf.dll"

Restart your WMI, and Exchange services, this should fix the problem.

Other problems may manifest so make sure to look into those as well.

This solution was found at:

This also fixed the stopped services problem (failed because they relied on the failing .Net/WMI service). Also freed up memory.

Further problems manifested:


Event Type: ErrorEvent Source: DCOMEvent Category: NoneEvent ID: 10005Date: 20/11/2008Time: 9:15:59 AMUser: NT AUTHORITY\SYSTEMComputer: SERVERDescription:DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service WinMgmt with arguments "" in order to run the server:{8BC3F05E-D86B-11D0-A075-00C04FB68820}


This is related to the above. The registry entry is for WMI, but in your case it may be something different.

To fix it, run "services.msc /s" from START >> RUN

Then restart the manual services for WMI (BITS is reliant on WMI, restart that too).
Then restart the automatic service for WMI and it should be good.

This solved my second problem.

Further Problem still:

Event Type: WarningEvent Source: PerflibEvent Category: NoneEvent ID: 2003Date: 20/11/2008Time: 10:26:42 AMUser: N/AComputer: SERVERDescription:The configuration information of the performance library "C:\WINNT\system32\w3ctrs.dll" for the "W3SVC" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.


Solution credited from:

This problem doesn't happen if you had chosen NTFS, or installed IIS later.

To resolve the problem:

1. Open a CMD prompt.

2. Type the following commands:

cd /d %SystemRoot%\System32
unlodctr w3svc
unlodctr asp
unlodctr inetinfo
unlodctr msftpsvc
lodctr w3ctrs.ini
lodctr axperf.ini
lodctr infoctrs.ini
lodctr ftpctrs.ini

You may want to make a batch file out of it, to speed things up. You can watch the event viewer, to see what is actually happening :)

Further Problem Still:

This seemed to clear up all things in the application log, at least in the next few minutes, however when I restarted WMI to ensure the process's that relied on WMI would be ok, one further error occurred.

Event Type: ErrorEvent Source: MSExchangeSAEvent Category: Monitoring Event ID: 9102Date: 20/11/2008Time: 11:37:20 AMUser: N/AComputer: SERVERDescription:The MAD Monitoring thread was unable to read the state of cluster resources, error '0x80080008'.
For more information, click


I have just written this one off, as MAD trying to do something, while shutting down..? Immediately following this error MAD is initialising and starts up. (As a result of restarting MS Exchange Management with WMI).

Further problems:

Event Type: Warning
Event Source: Perflib
Event Category: None
Event ID: 1016
The data buffer created for the "EXOLEDB" service in the "C:\Program Files\Exchsrvr\bin\exodbpc.dll" library is not aligned on an 8-byte boundary. This may cause problems for applications that are trying to read the performance data buffer. Contact the manufacturer of this library or service to have this problem corrected or to get a newer version of this library.


This website, said it was not an error worth worrying about.

Further problems:

There were some other errors, but I am going to ignore them until I reboot and assess the services to see if they are all starting ok..

This post shall be returned to.

No comments: