Solving WmiApRpl and BITS errors with SharePoint 2013 on Windows Server 2012

Friday, May 3, 2013

Sharepoint SharePoint 2013

I have been searching for a way to get rid of some performance counter errors (WmiApRpl and BITS) on my SharePoint 2013 installation for a while but couldn't find the answer. Today I decided to have a look with Process Monitor and finally found a solution.

The w3wp process tries to access to registry keys but does not have the permissions.

After granting the WSS_WPG group full control(you probable can get away with a little less) to the following registry keys, the errors went away.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BITS\Performance
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WmiApRpl\Performance

And that's it!

Cheers,

Wesley

8 Comments

Reply

Thanks for the finding on the registry keys, but it's enough to give Read permission on these keys.

lgp1985 - Tuesday, September 16, 2014 12:57:01 PM

Reply

I don't understand how to give permissions to the Registry keys listed here.

mike carrieri - Wednesday, February 4, 2015 6:52:07 PM

Reply

Hi,

I granted read permission to those reg keys but still getting same issue, below last event generated few days ago:

Event ID 1008 : 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.

brix - Tuesday, March 31, 2015 1:24:32 PM

Reply

right click on the registry key then select permissions, in permission popup, click add, select the user or the group then selct access level(full access, read or special permissions)

brix - Tuesday, March 31, 2015 1:27:27 PM

Reply

Thank you this solved my problem!

Louis - Monday, April 20, 2015 12:45:08 PM

Reply

if you want to apply all sharepoint permissions run this command : PSConfig.exe -cmd secureresources

christophe - Wednesday, June 17, 2015 1:12:49 PM

Reply

This worked for all of 1 whole day. Today (day 2), the error has reappeared.

CJ - Thursday, December 10, 2015 5:20:48 PM

Reply

Awesome, sorted it!

Christian - Sunday, December 13, 2015 7:48:37 AM

Comments have been disabled for this content.