Siv
asked on
Perflib errors SBS 2003
Hi,
Since some updates were applied last week to SBS 2003 I am getting quite a few error messages like these:
The configuration information of the performance library "C:\WINDOWS\system32\perft s.dll" for the "TermService" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
The configuration information of the performance library "C:\WINDOWS\system32\asppe rf.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.
Does anyone know how I can fix this error?
Siv
Since some updates were applied last week to SBS 2003 I am getting quite a few error messages like these:
The configuration information of the performance library "C:\WINDOWS\system32\perft
The configuration information of the performance library "C:\WINDOWS\system32\asppe
Does anyone know how I can fix this error?
Siv
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
DrDave242
I managed to get logged into the server and run the command
lodctr /T:TermService
and
lodctr /T:ASP
Which are the two that keep appearing in teh logs so I will monitor the reports and see if it works over the next couple of days.
Cheers,
Siv
I managed to get logged into the server and run the command
lodctr /T:TermService
and
lodctr /T:ASP
Which are the two that keep appearing in teh logs so I will monitor the reports and see if it works over the next couple of days.
Cheers,
Siv
ASKER
DrDave242,
I have gone for a week now and the errors are not in the logs any more so you have found the fix, thanks for that, points awarded and question closed.
Siv
I have gone for a week now and the errors are not in the logs any more so you have found the fix, thanks for that, points awarded and question closed.
Siv
ASKER
No errors appearing since this fix was applied.
ASKER
As you say this looks highly promising, I will try this fix and report back when the next set of logs come in and the issue has gone.
Thanks for your help with this.
Siv