Friday, February 10, 2012
Retabbed
Login | Register
블로그
  Search
블로그 목록
블로그 아카이브
블로그 검색
aspnet_perf.dll 프로시져 오픈에 실패했다는 로그가 산더미로..
Location: Blogs불나방의 소프트 블로그    
Posted by: 불나방 2008-08-03 오전 8:15

The Issue 
There are some registry entries missing that define the Counter ID Range and Help ID Range.

On my Win2000 Server running SBS 2000 I found a couple of bad performance counters in the Registry at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET\Performance
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET_2.0.50727\Performance

Both of them were missing entries for First Counter, Last Counter, First Help, and Last Help

What Caused it?  
I haven't been able to track that one down yet.  I noticed it after I installed .Net 2.0.  I ran .net 2.0 SP 1 but that didn't change anything.

How do I fix it?
I can offer two ways to work around this issue, Disable the Performance Indicator or Replace the Registry Values.To Disable the Indicator:
1.  Download the 'Extensible Performance Counter List (exctrlst.ext) tool from
http://support.microsoft.com/kb/927229
2.  Run the tool, Sort by Service, look for performance keys that have   'Not Found' in the Counter and Help ID ranged.
3.  Uncheck the 'Performance Counters Enabled' box for each one you find.
4.  Restart the 'Windows Management Instrumentation' Service

Add the Registry Values:  (Not Recommended)
1.  Run Registry File to Add Missing Keys.  (You might need to modify this if you have different performance keys missing data)
2.  Restart the 'Windows Management Instrumentation' Service.

I pulled some registry values from another windows 2000 server and restarted the 'WMI' Service.  I got some positive results.  I don't see any more Event 1008 messages but I did get a couple of warning messages:
- The data buffer created for the "EXOLEDB" service in the "D:\Exchsrvr\bin\exodbpc.dll" library is not aligned on an 8-byte boundary.     Source = Perflib, Event ID: 1016
- Two other warning messages from WinMgmt, Event ID 39 and 35

I don’t recommend this as your final solution but it’s always fun to roll the dice and see what happens.  Personally I just disabled the values on my server.

The registry script is:
---------------------------------------------
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET\Performance]
"Last Counter"=dword:00002568
"Last Help"=dword:00002569
"First Counter"=dword:000024aa
"First Help"=dword:000024ab
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET_2.0.50727\Performance]
"Last Counter"=dword:000024a8
"Last Help"=dword:000024a9
"First Counter"=dword:000023ea
"First Help"=dword:000023eb
---------------------------------------------------
 I found a lot of message thread on the subject so it's a issue that's driving a lot of admin's crazy.  I hope this helps. 

Permalink |  Trackback
Terms | Privacy | host
Copyright 2005 Code99.NET
 | 아티클 | 자료실 | 블로그 | Q&A | 관리자에게