The performance counters for the WMIAPRPL (WMIAPRPL) service were successfully loaded. The record data contains a new index value assigned to the service.
This error occurs because a competition problem occurred while processing the counter list. When LoadPerf.dll reads the index value of the last counter and other counters are added, the new meter
The index value of the number is larger than the index value of the last counter, so LoadPerf.dll that the counter value is incorrect and records the next event log. Because LoadPerf.dll has encountered this error
A retry is made and the new counters are read successfully, so this error does not cause any usage impact after retrying.
The workaround is to type: lodctr/r at the command prompt to automatically rebuild the performance counter string table
Performance counter information is saved in the following location:
Registration form:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows Ntcurrent VersionPerflib09
2 files in the system folder:
%systemroot%system32perfc009.dat and
%systemroot%system32perfh009.dat
The rebuild counter value steps are as follows:
The two files on the system installation disk: DriveLetter:i386perfc009.da_ and DriveLetter:i386perfh009.da_, respectively, are expanded into: Perfc009.dat and
Perfh009.dat (DriveLetter on behalf of the System installation disk letter), and then copy to the System folder%systemroot%system32, replace the original 2 files. Expand the life of a file
The order format is: Expand Perfc009.da_ Perfc009.dat.
Open Registry Editor and navigate to:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows ntcurrentversionperflib items.
Modifies 2 subkey values, Lastcounter to decimal 1846,lasthelp to decimal 1847.
And then navigate to the Hkey_local_machinesystemcurrentcontrolsetservices item.
All performance subkeys are found, if the Performance subkey contains the following key values, delete:
Firstcounter
Firsthelp
Lastcounter
LastHelp
When you're done, the next step is to add the performance counter value again:
1. Open a Command Prompt window.
2. Transfer to the System folder by entering the CD%systemroot%system32 command.
3. Through the findstr drivername *.ini command, find all drivers that need to be loaded.
4. Note the list of the INI files found
5. Then reload all the found INI files through the loadctr inifile command
6. Finally restart the computer
--------------------------------------------------------------------------------------------------------------- ----------
This problem has plagued many administrators, causing the server to automatically restart frequently.
Problem Description:
Server Event Viewer-The following error occurred in the system
The performance string in the performance registry value is corrupted when processing an performance extension counter provider. The BaseIndex value in the performance registry is the first in the data section
DWORD value, the Lastcounter value is the second DWORD in the data section, and the LastHelp value is the third DWORD in the data section.
Failed to unload the performance counter string for service WMIAPRPL (WMIAPRPL). The error code is the first DWORD value in the data section.
The counters index range for the service Systemcurrentcontrolsetservicesserv-u-countersperformance has been corrupted. The first DWORD value in the data section contains
There is the first index used, and the second DWORD in the data section contains the last index used.
Failed to install performance counter string for service Serv-u-counters (% 2). The error code is the first DWORD value in the data section.
Workaround:
1th step: In the "Start"--"run" input cmd to DOS command line mode
Running in command line mode: LODCTR/R
LODCTR/R This command to rebuild the performance counter string table in the registry
Step 2nd: Confirm if there is a serv-u
Open the registry with Regedit
Key found: systemcurrentcontrolsetservicesserv-u-countersperformance
Check to see if the counter and last counter exist, and whether the data is irregular
When the discovery does not exist or the data is abnormal, upgrade the Serv-u software to the latest version, see again, found that the missing key and the corresponding values are automatically fully filled.
The 3rd step, if you go through 1, 2 steps still to solve the problem in the future, you can check the machine cooling problem, if the machine CPU fan, chassis internal cooling fan, the video card fan does not work, can also
The
can cause the machine to restart frequently, so the problem here is done.