Warning Preflib service does not match the trusted performance library in reg
Question
Friday, April 15, 2016 5:02 PM
Hello,
While review my event logs I came across this warning. I need to take some action on this, I'm just not sure what. Any help would be greatly appreciated.
Log Name: Application
Source: Perflib
Event ID: 2003
The configuration information of the performance library "perf-MSSQLSERVER-sqlctr10.50.1600.1.dll" for the "MSSQLSERVER" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
I was reading on one site, that I should reinstall the perf-MSSQLSERVER-sqlctr10.50.1600.1.dll. If this is true, what can I find the file for down load from microsoft?
Thank you!
David92595
All replies (6)
Tuesday, April 19, 2016 7:19 AM ✅Answered
The configuration information of the performance library "perf-MSSQLSERVER-sqlctr10.50.1600.1.dll" for the "MSSQLSERVER" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
Hi David92595,
The above error indicates the <<Service name>>\Performance\Library Validation Code value is invalid. This code is generated by lodctr as a checksum of the performance counter DLL. If the DLL has been updated outside lodctr the value won’t match and the error is logged.
Please follow the steps in the blog below to troubleshoot the performance counter issue.
https://blogs.msdn.microsoft.com/psssql/2009/03/03/troubleshooting-sql-server-2005-2008-performance-counter-collection-problems/
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support
Friday, April 15, 2016 6:57 PM
Hello,
Please read the following articles:
https://technet.microsoft.com/en-us/library/cc727150%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
https://support.microsoft.com/en-us/kb/932813
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Friday, April 15, 2016 7:07 PM
Thank you Alberto for the response.
I had already read the first article. I'm just not sure if it is safe to trust the dll. Is there anyway to verify or re-download the dll? The second article was reassuring, I'm running SQL Server 2008 R2 (probably should have mentioned that). Any idea's where I can get a fresh down load from a Microsoft site? I work under banking regulations, so everything has to be documented and from trusted sources...aka the hard way.
David92595
Tuesday, December 19, 2017 11:37 PM | 3 votes
The above error indicates the <<Service name>>\Performance\Library Validation Code value is invalid. This code is generated by lodctr as a checksum of the performance counter DLL. If the DLL has been updated outside lodctr the value won’t match and the error is logged.
Please follow the steps in the blog below to troubleshoot the performance counter issue.
https://blogs.msdn.microsoft.com/psssql/2009/03/03/troubleshooting-sql-server-2005-2008-performance-counter-collection-problems/
I see this issue just after installing MS SQL Server 2017 Express on a fully patched MS Windows Server 2012 R2. The warning is logged to Event Log once a day.
The steps given in the blog article are partly out of date because WinPriv.exe does not exist on Windows Server 2008 / Windows Vista and newer. Windows now uses WmiPrvSE.exe instead. Some users (me included) noticed that more than on instance of WmiPrvSE.exe run on their system. So, how to determine the PID to use with "winmgmt /resyncperfctr" command?
I must add that it is a shame that Microsoft programmers have not yet fixed the issue 8+ years old.
Wednesday, April 11, 2018 7:00 PM | 2 votes
The above error indicates the <<Service name>>\Performance\Library Validation Code value is invalid. This code is generated by lodctr as a checksum of the performance counter DLL. If the DLL has been updated outside lodctr the value won’t match and the error is logged.
Please follow the steps in the blog below to troubleshoot the performance counter issue.
https://blogs.msdn.microsoft.com/psssql/2009/03/03/troubleshooting-sql-server-2005-2008-performance-counter-collection-problems/I see this issue just after installing MS SQL Server 2017 Express on a fully patched MS Windows Server 2012 R2. The warning is logged to Event Log once a day.
The steps given in the blog article are partly out of date because WinPriv.exe does not exist on Windows Server 2008 / Windows Vista and newer. Windows now uses WmiPrvSE.exe instead. Some users (me included) noticed that more than on instance of WmiPrvSE.exe run on their system. So, how to determine the PID to use with "winmgmt /resyncperfctr" command?
I must add that it is a shame that Microsoft programmers have not yet fixed the issue 8+ years old.
Did you find a solution? I'm now encountering the errors on SQL Server 2017 on Server 2016 -- after patch Tuesday yesterday.
Tuesday, April 2, 2019 5:15 PM
I too see this after server updates. I am also unable to run reports and receive and .rs Process Aborting error.