This morning when I checked a procedure night working on Microsoft Active Directory, I noticed something was wrong: this procedure was strangely still running and proceed with extreme slow and suspicious. Cosi 'after consultation with the various logs (Windows Event Viewer and those generated by the application) I realized that the problem lay elsewhere: the only other game elemnto in addition to the machine that is running the application on a daily basis, and 'reference to the Domain Controller. I connect to the Domain Controller and I see the Windows Application log fully saturated red and the error:
Event Type: Error Event Source
: Perflib
Event Category: None
Event ID: 1008
Date: 17/07/2008
Time: 13:29:04
User: N / A
Computer: XXXXXXXX
Description:
The Open Procedure for service "ASP.NET" in DLL
"C: \\ WINNT \\ Microsoft.NET \\ Framework \\ v2 .0.50727 \\ aspnet_perf.dll "failed.
Performance data for this service are not available.
The status code returned is DWORD 0.
Data:
0000: 05 40 00 80. @. €
Fortuna:) and the error message 'eloquent enough: there are problems with the performance counters of aspnet.
Before you begin, however, consult your network to check for any notes on the Microsoft KB or forum post or technical, you never know someone may 'have had the same problem and maybe has even solved ... and in fact after a brief search on google I find the post http://www.archivum.info/microsoft.public.it.winserver/2008-07/msg00748.html which, incidentally, describes exactly my problem.
Basically the solution is to disable performance counters to since it is an aspnet un'issue note to Microsoft and which, at the time of writing, have not yet released patches (for the sake of cornaca I must say that the system affected by error and 'a Windows 2000 SP4, an operating system no longer in use and out of maintenance). Here are the steps I have undertaken to solve the problem:
- from the command prompt I brought v2.0 * folder. NET Framework
- I ran the command aspnet_regiis-ua
- I rebooted the machine The problem
0 comments:
Post a Comment