XP x64 Pro: Administrative Tools->Performance dead ?

[Guest Skybuck Flying]

Hello,

 

It seems the performance tool is dead on XP x64 Pro.

 

I see numbers only, instead of counter names like on x86 ?

 

Seems like the tool is dead on XP x64 Pro ?

 

Bye,

Skybuck.

[Guest Skybuck Flying]

Re: XP x64 Pro: Administrative Tools->Performance dead ?

 

According to microsoft corruption can occur which is not good to start with,

and then complex repair must be done:

 

http://support.microsoft.com/kb/300956

 

Some automatic repair tool would be nice.

 

Or don't let it get corrupt in the first place !

 

^^^ which means bug fixes ^^^

 

Bye,

Skybuck.

[Guest Skybuck Flying]

Re: XP x64 Pro: Administrative Tools->Performance dead ?

 

Text from link:

 

"

How to manually rebuild Performance Counter Library values

View products that this article applies to.

Article ID:300956

Last Review:March 2, 2007

Revision:10.4

 

This article was previously published under Q300956

Important This article contains information about how to modify the

registry. Make sure to back up the registry before you modify it. Make sure

that you know how to restore the registry if a problem occurs. For more

information about how to back up, restore, and modify the registry, click

the following article number to view the article in the Microsoft Knowledge

Base:

256986 (http://support.microsoft.com/kb/256986/) Description of the

Microsoft Windows registry

SUMMARY

This article describes how to manually rebuild the performance counter

library values.

 

Important The information in this article only applies to English-language

versions of Windows 2000.

MORE INFORMATION

Warning Serious problems might occur if you modify the registry incorrectly

by using Registry Editor or by using another method. These problems might

require that you reinstall your operating system. Microsoft cannot guarantee

that these problems can be solved. Modify the registry at your own risk.

 

When you use the System Monitor tool, some counters may be missing or do not

contain counter data. The base set of performance counter libraries may

become corrupted and may need to be rebuilt along with any extensible

counters. This behavior may occur if certain extensible counters corrupt the

registry, or if some Windows Management Instrumentation (WMI)-based programs

modify the registry.

 

Extensible counter information is stored in both of the following

locations: •The following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Perflib\009

•The %Systemroot%\System32\Perfc009.dat file and the

%Systemroot%\System32\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:\i386\perfc009.da_ and at DriveLetter:\i386\perfh009.da_.

Replace the files that are in the %Systemroot%\System32 folder.

2.Start Registry Editor, and then locate the following key in the registry:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\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_MACHINE\System\CurrentControlSet\Services

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%\System32, 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:drivername=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\system32

lodctr /R

Note /R is uppercase.

 

Windows Server 2003 rebuilds all the counters because it reads all the .ini

files in the C:\Windows\inf\009 folder for the English operating system.

 

Note If you are running a Cluster or Datacenter product, you must fail over

the node to refresh the counter list after doing the preceding steps for

both base counters and extensible counters.

 

Note On systems that are running applications that add their own performance

counters, such as Microsoft Exchange or SQL Server, the .ini file that is

used to load the performance counter may not be located in

%Systemroot%\System32. These .ini files can usually be found under the

applications folder structure.

 

Note If you receive an error message about the performance library when you

use the preceding steps, you may have to unload and reload the IIS

performance dynamic link libraries (DLLs). For more information about how to

do this, click the following article number to view the article in the

Microsoft Knowledge Base:

267831 (http://support.microsoft.com/kb/267831/) Event ID 2003 Warning

message logged when loading performance counters

 

"

 

I performed steps 1 to 3 and skipped the rest <- to much work.

 

lodctr /R

 

^ Trying it now to see if I can get basic system counters back.

 

Yes it worked, cool/good !

 

Bye,

Skybuck.