Page 1

Perflib (WmiApRpl and BITS) on Server2012 and 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.



Auto Update on SharePoint servers

Somewhere in October Microsoft decided to add a SharePoint update to the Windows Update system. This caused some Sharepoint servers that had enabled Auto Update to stop working and throwing errors all around the place.

Now on most servers we have disabled the following function:
Give me updates for other Microsoft products when I update Windows


This should disallow Windows Update to update Office applications like SharePoint, except it didnt do this for the update that Microsoft did sneak into a Windows update!

This resulted in a new Best Practice for our SharePoint servers to not Auto Update the SharePoint servers, we know this could be a possible Security risk, but it also could lead to a non working SharePoint Farm!


Let Windows only download the updates and manually install them so you can check for hidden updates. You can change this in the Control Panel –> System Security –> Windows Update, and just change the settings there.


A System Restart from a previous installation or update is pending.

When you try to install Sharepoint 2013 Server, you will get the message that there still is a System Restart pending from a previous installation.

Setup Errors






To solve this issue you can edit a REGkey and continue with the setup.

Step 1

Open regedit, go to Start and select Run (or use Windows Key + R), and enter “regedit”

Step 2

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

Step 3

Rename the key “PendingFileRenameOperations” to “PendingFileRenameOperations_OLD”

Step 4

Do not reboot your system, but just run the Setup again and install Sharepoint 2013 Server as usual.


Install Sharepoint 2013 server on Local Machine

After the installation of Sharepoint 2013 Server edition you have to run the Product Configuration Wizard to setup the Config database. In Sharepoint 2013 Server it is not possible to use a local account to setup the database.

However there is a workaround. As PowerShell is our friend in a lot of cases, here it is also our friend.

Start an elevated Sharepoint 2013 Management Shell and use the command


From there you can configure the Config database. After this is done, run the Product Configuration Wizard again, and make sure to select Do not disconnect from this server farm.

Now you can follow the installation steps to configure Sharepoint 2013