Programming, SharePoint, Software, Technology, Windows 2012

Dealing with Event ID 10016 System Error Logs with a Fresh SharePoint Installation

Event 6398
Event ID 10016 System Errors

When you first set up SharePoint 2016 on a Windows 2012 machine, you’ll see a large number of Windows System Event Log errors classified as Event ID 10016. Microsoft’s documentation indicates that these are not going to cause problems with SharePoint and they can be ignored… except for the fact that nightly (in my case it was consistently around 12:50am) you’ll get a cascade of new errors clogging up your event logs.

Obviously no-one wants their event logs clogged with false alarms, so you’ll want to figure out how to stop these from being generated. I experienced these Event ID 10016 errors with SharePoint 2016 on Windows 2012, but I believe they also happen with other versions of SharePoint and Windows.

In debugging the 10016 Windows System Event Log errors I noticed that two main errors are classified under the same ID. Both are related to DCOM permissions issues assigned to the SharePoint administrative account that is listed under the User section in each error.

The first 10016 error  is related to CLSID {000C101C-0000-0000-C000-000000000046} and is explained in in this TechNet article:

https://social.technet.microsoft.com/Forums/ie/en-US/3313c6c5-383a-4051-a22a-04452f87642a/the-machinedefault-permission-settings-do-not-grant?forum=sharepointsearch

The second error is related to CLSID {61738644-F196-11D0-9953-00C04FD919C1} and is explained in detail in this Microsoft help article:

https://support.microsoft.com/en-ca/help/920783/event-id-error-messages-10016-and-10017-are-logged-in-the-system-log-a

Before you Start: Update the Registry to Allow your Account to Make the Needed DCOM Changes

First: Escalate your Account permissions so you can save DCOM changes.

Unless you installed Windows, it is likely your account doesn’t have permissions to make the necessary updates to fix these two errors. Each error requires a small change in the Windows registry in order for you to be able to edit the DCOM permissions.

Registry Settings For Error #1:

  1. On the server press the Windows+R and type regedit to bring up the registry editor
  2. Navigate the hierarchy to find the key: HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\APPID\{000C101C-0000-0000-C000-000000000046}
  3. Right click the key {000C101C-0000-0000-C000-000000000046} and choose Permissions
  4. Click the Advanced option button (at the bottom)
  5. In the Advanced settings, at the top, click the option to Change the owner
  6. Your best bet is to set this to the local machine Administrators group since you are likely part of this
  7. Click OK to save your changes
  8. Now in the Permissions window, select the Administrators group and check the Full Control option
  9. Click OK to save your changes

Registry Settings For Error #2:

This error is related to activation permissions for the IIS WAMREG admin Service The admin service goes by CLSID {61738644-F196-11D0-9953-00C04FD919C1} in the registry. So the steps to be able to modify this DCOM setting are almost identical as the steps for Error #1 above:

  1. On the server press the Windows+R and type regedit to bring up the registry editor
  2. Navigate the heirarchy to find the key: HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\APPID\{61738644-F196-11D0-9953-00C04FD919C1}
  3. Right click the key {61738644-F196-11D0-9953-00C04FD919C1} and choose Permissions
  4. Click the Advanced option button (at the bottom)
  5. In the Advanced settings, at the top, click the option to Change the owner
  6. Your best bet is to set this to the local machine Administrators group since you are likely part of this
  7. Click OK to save your changes
  8. Now in the Permissions window, select the Administrators group and check the Full Control option
  9. Click OK to save your changes

Now that you’ve made these changes, close the Registry Editor and get ready to change the DCOM configurations.

Making the DCOM Configuration Changes:

Now that you have updated the registry permissions to allow you to make DCOM changes, you can use DCOMCnfg to update the permissions for each of these errors.

DCOM Permissions For Error #1

  1. On the server press the Windows+R keyboard shortcut and type dcomcnfg
  2. Then browse the heirarchy Component Services\Computers\My Computer\DCOM Config
  3. Scroll down the list until you see {000C101C-0000-0000-C000-000000000046}
  4. Right click on {000C101C-0000-0000-C000-000000000046}
  5. Select Properties
  6. In the IIS WAMREG admin Service Properties Popup, click the Security tab
  7. Click the Customize option under the top Launch and Activation Permissions heading
  8. Click the Edit button
  9. Add the group or user that is causing the problem in the event logs using the Add button
  10. Under Permissions, check the boxes to give that user or group: Local Launch and Local Activation permissions
  11. Click OK to save your changes

DCOM Permissions For Error #2

  1. On the server press the Windows+R keyboard shortcut and type dcomcnfg
  2. Then browse the heirarchy Component Services\Computers\My Computer\DCOM Config
  3. Scroll down the list until you see IIS WAMREG admin Service
  4. Right click on IIS WAMREG admin Service
  5. Select Properties
  6. In the IIS WAMREG admin Service Properties Popup, click the Security tab
  7. Click the Customize option under the top Launch and Activation Permissions heading
  8. Click the Edit button
  9. Add the group or user that is causing the problem in the event logs using the Add button
  10. Under Permissions, check the boxes to give that user or group: Local Launch and Local Activation permissions
  11. Click OK to save your changes
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s