Using the ToolKit and viewing the event viewer I noticed repeat error messages [especially when WHS is rebooted]:
These errors only occured after a series of windows updates.
Error 1:
Perflib Warning None 2003 N/A SERVER "The configuration information of the performance library ""C:\WINDOWS\system32\inetsrv\w3ctrs.dll"" for the ""W3SVC"" service does not
match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted."
Error 2:
Perflib Warning None 1016 N/A SERVER "The data buffer created for the ""VOLPERF"" service in the ""C:\WINDOWS\system32\volperf.dll"" library is not aligned on an 8-byte boundary. This may cause problems for applications that are
trying to read the performance data buffer. Contact the manufacturer of this library or service to have this problem corrected or to get a newer version of this library."
[ At Least this one says it is bad ]
Error 3:
Perflib Warning None 2003 N/A SERVER "The configuration information of the performance library ""C:\WINDOWS\system32\aspperf.dll"" for the ""ASP"" service does not match the
trusted performance library information stored in the registry. The functions in this library will not be treated as trusted."
======
Partial solution: [ for Error 1 and Error 3 ] ... but still IMHO
[The DLL is screwed up = Developer issue ]
Source:
" You can learn more about Lodctr at
Microsoft TechNet Loctr (the /T flag is not described on the site but is used to specify a service name which then sets the service as Trusted."
<Command Prompt> [ Through Remote Desktop or ToolKit Command Prompt]
lodctr /T:W3SVC
lodctr /T:ASP
Note: This should also be applicable to other Dll / Service errors fitting the error text matching "....
service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted."
======
Research on Error 2: <SomeServiceOrDll>.dll library is not aligned on an 8-byte boundary. shows it is NOT the Windows Home Server [or something I did] but a coding issue in the Dll itself .. the "solution
is to TURN off Error reporting using a registry key"
When you use Windows NT Performance Monitor to check the performance of the Microsoft.....
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Perflib
On the Edit menu, click Add Value, and then add the following value:
Value Name: Configuration Flags
Data type: REGDWORD
Value: 0x01
[ A.K.A.
Disable Counters]
0x01 - Do not test for data buffer alignment errors. Suppresses 1016 event.
======
Regards.
