Juan:
I am not confident to do it. What should I do? I have both framework 1.1 and
2.0, and server application running. the instruction is in the following:
......
Extensible counter information is stored in both of the following locations:
• The following registry key:
HKEY_LOCAL_MACH INE\Software\Mi crosoft\Windows NT\Current Version\Perflib \009
• The %Systemroot%\Sy stem32\Perfc009 .dat file and the
%Systemroot%\Sy stem32\Perfh009 .dat file.
To rebuild the base performance counter libraries manually: 1. Expand the
Perfc009.dat file and the Perfh009.dat file. These files are located on the
Windows 2000 CD-ROM. The compressed files are found at
DriveLetter:\i3 86\perfc009.da_ and at DriveLetter:\i3 86\perfh009.da_ . Replace
the files that are in the %Systemroot%\Sy stem32 folder.
2. Start Registry Editor, and then locate the following key in the registry:
HKEY_LOCAL_MACH INE\Software\Mi crosoft\Windows NT\CurrentVersi on\Perflib
3. In the registry, change the LastCounter value to 1846 (decimal), and
change the LastHelp value to 1847 (decimal).
4. Locate the following registry key to search for services that have a
Performance subkey:
HKEY_LOCAL_MACH INE\System\Curr entControlSet\S ervices
5. Remove the following values from the Performance subkey (if they exist):
• FirstCounter
• FirstHelp
• LastCounter
• LastHelp
You can also use the Exctrlst.exe tool to locate the performance counter
dynamic-link library files (DLLs) that are installed, and then access the
registry to remove the DWORD values. You now have a workable performance
registry that contains only system base counters.
After you have completed this procedure, you must re-add the extensible
counters from the list of services. Before you do so, however, you must
identify the .ini file that is used to load the counters: 1. Open a command
prompt window.
2. At the command prompt, type cd %Systemroot%\Sy stem32, and then press
ENTER.
3. At the command prompt, type findstr drivername *.ini, and then press
ENTER.
4. Note the name of the .ini file for each drivername in the list.
5. At the command prompt, type the following line, and then press ENTER:
lodctr inifile
where inifile is the name of the .ini file for the driver that you want to
reload.
For example, if you want to reload the ASP driver, the list that you noted
in step 4 shows that Axperf.ini is the .ini file for the ASP driver
(axperf.ini:dri vername=ASP). Therefore, to reload the ASP driver, type lodctr
axperf.ini at the command prompt, and then press ENTER.
6. Repeat step 5 for each .ini file in the list.
7. Restart your computer.
To rebuild all Performance counters including extensible and third party
counters in Windows Server 2003, type the following commands at a command
prompt. Press ENTER after each command.
cd \windows\system 32
lodctr /R
Note /R is uppercase.
......
"Juan T. Llibre" wrote:
You can use the KB article linked to below to rebuild your performance counters
or contact Microsoft Product Support Services and request to speak with a
Support Engineer in the Platforms Performance group to get a tool call PCRW
(Performance Counter Rebuild Wizard) that automates the process.
300956 How to manually rebuild Performance Counter Library values
http://support.microsoft.com/?id=300956
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
=============== =============== ========
"david" <da***@discussi ons.microsoft.c omwrote in message news:69******** *************** ***********@mic rosoft.com...
The same error messages full out the application event log.
---
"The open procedure for service "ASP.NET" in DLL
"C:\WINNT\Micro soft.NET\Framew ork\v2.0.50727\ aspnet_perf.dll " failed.
Performance data for this service will not be available. Status code
returned is data DWORD 0.
Data (words): 0000: 80004005
---
I have not found this error before I installed .net framework 2.0.
My system is windows 2000 server.
Thanks for any help.
David
