Quantcast
Channel: SharePoint 2013 - Setup, Upgrade, Administration and Operations forum
Viewing all articles
Browse latest Browse all 21070

SharePoint 2013 perflib errors - Anyone actually found the cause of these errors?

$
0
0

Hi All!

I guess we have all seen these errors flooding our Application Event log?:

The Open Procedure for service "WmiApRpl" in DLL "C:\Windows\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

and:

The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

I'm wondering if anyone has found the root cause for these errors?
I have tried running the initial farm configuration from both PS as well as the wizard and both ending up with these events on server reboot as well as when the central admin or any other SharePoint web application is starting.

These errors itself doesn't seem to affect the SharePoint installation, since everything  is working fine.
But as a systemadministrator i hate to see errors in the Event logs, at least i wan't to know if they in fact could affect the operation of the system..

I have noticed that if I place all serviceaccounts used within the local administrators group on the server the number of these events is greatly reduced, which makes me Think that is some kind of permissions issue not being set for the service accounts on the local SharePoint server?

I have searched a lot on the web on this issue, where you can find anything from rebuilding all performance counters to simply disable these.

Can these errors safely be ignored and turned off?

// Philip


Viewing all articles
Browse latest Browse all 21070

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>