Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

DCOM event 10016: "The application-specific permission settings do not grant Local Activation permission for the COM Server application"

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

A System log full of event 10016 from Microsoft-Windows-DistributedCOM looks like a permissions fault, and it reads like one. Microsoft's page says otherwise. It states that "These 10016 events are recorded when Microsoft components try to access DCOM components without the required permissions. In this case, this behavior is expected and by design", and that "These events can be safely ignored because they don't adversely affect functionality".

The useful work is to read the event's fields, confirm it matches the pattern Microsoft describes, and decide whether to leave it, hide it in Event Viewer, or take it further. Everything below that runs on the server only reads.

What the error means

Microsoft's page "DCOM event ID 10016 is logged in Windows" (dated 2026-05-19) applies to supported versions of Windows Client and Windows Server, and shows sample events from Windows 10, Windows Server 2019 and Windows Server 2016. Each sample has Source Microsoft-Windows-DistributedCOM and Event ID 10016. The description, in two of its forms, reads:

  • "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {…} and APPID {…} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
  • "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {…} and APPID {…} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) …"

The samples on the page name NT AUTHORITY\SYSTEM, NT AUTHORITY\LOCAL SERVICE, and an ordinary user running in the Microsoft.Windows.ShellExperienceHost application container.

Microsoft's cause is a coding pattern. The code first tries to access the DCOM components with one set of parameters; "If the first attempt is unsuccessful, it tries again with another set of parameters. The reason why it doesn't skip the first attempt is because there are scenarios where it can succeed. In those scenarios, it's preferable." So the logged failure is the first attempt, and the second attempt follows it.

Likely causes

Cause What you see How to confirm
A Microsoft component's first attempt, by design Repeated 10016 events with the same CLSID, APPID and SID, with no loss of function The CLSID, APPID and SID in the event match a sample or a known repeat; nothing else fails
The same event for a component Microsoft's page does not list 10016 with a CLSID or APPID that is not one of the page's samples Compare param4 (CLSID), param5 (APPID) and param8 (SID) with your other events
Something is failing at the same time An application error or user complaint at the time of the 10016 Microsoft's page describes no 10016 case that causes a failure, so look for other events from that time

Microsoft's page names only the first cause. The second and third rows are the checks that tell you whether the page's statement applies to your server.

Prove the cause before changing anything

All of these only read. In an elevated Command Prompt, list the five most recent 10016 events in readable form. The wevtutil qe syntax is on Microsoft's wevtutil page, which shows /c: for the count, /rd: for direction and /f: for format, and the XPath selector *[System[(EventID=10016)]] is the one Microsoft's own page uses:

wevtutil qe System /q:"*[System[(EventID=10016)]]" /c:5 /rd:true /f:text

In PowerShell, Microsoft's Get-WinEvent page documents -FilterHashtable with a log name and an event ID, and -MaxEvents:

Get-WinEvent -FilterHashtable @{ LogName='System'; Id=10016 } -MaxEvents 5

For each event, write down three values. Microsoft's page names the fields: "param4 corresponds to the COM Server application CLSID", "param5 corresponds to the APPID" and "param8 corresponds to the security context SID". Those are the values you need to describe one repeating event exactly.

Then check two things from the events themselves. First, is the same CLSID, APPID and SID repeating? If so, that is the kind of repetition the page's filter is built for. Second, does anything fail at the same moment? Microsoft's page says the events "don't adversely affect functionality", but a failure you can see is a reason to look at other events from that time and not at 10016 alone.

Example (illustrative): at contoso.com.au the server rds01 logs a 10016 event every few minutes. The event says the application-specific permission settings do not grant Local Activation permission to NT AUTHORITY\SYSTEM SID (S-1-5-18). The three values are the same in each event, and users report no problems. That matches the pattern in Microsoft's page, so the right answer is to leave the events, or hide them, and not to change permissions.

Fix

The fix Microsoft recommends is to do nothing: "These events can be safely ignored because they don't adversely affect functionality and are by design. It's the recommend action for these events."

If the events are in the way

Microsoft says that "advanced users and IT professionals can suppress these events from view in the Event Viewer." The page's method is to create a filter and manually edit the filter's XML query so that it selects the System log and suppresses the matching events. Its sample query suppresses events whose ID is 10016 and whose param4, param5 and param8 match given values, for example a CLSID, an APPID and S-1-5-18. Microsoft's Consuming Events page describes the structure the query uses: a structured XML query holds selectors and suppressors, and a suppressor contains an XPath expression that prevents events from being selected.

The page gives no click-by-click steps for creating the filter in Event Viewer. The filter changes what a view shows. Microsoft describes it as suppressing the events "from view", and the page does not say the events leave the log. A filter built from the exact values of one event hides only that pattern; the same query without them would match every 10016 event, including one nobody has read.

Risk: a suppression filter hides matching events from the view, so a filter that is too broad hides events nobody has read. Microsoft's page describes the filter and gives no way to remove it.

The event's three fields are what make a suppression precise: with all three values in the query, only the events you examined are hidden. Without them, the query matches every 10016 event, including one from a component Microsoft's page does not describe.

Changing DCOM permissions

Microsoft's page says you can also modify the permissions on DCOM components to prevent the error from being logged, and says "we don't recommend this method because" "These errors don't adversely affect functionality" and "Modifying the permissions can have unintended side effects." The event text itself says the permission can be modified using the Component Services administrative tool. Microsoft's page gives no steps for that change and no way back from it. Do not take the event's wording as a request to grant the permission.

Confirm the fix

  • If you chose to leave the events, there is nothing to confirm except that nothing else is failing. Run the wevtutil or Get-WinEvent check again after the period in which the problem was reported and read any event from the same time that is not 10016.
  • If you built a suppression filter, open the view and check that it hides only the events whose CLSID, APPID and SID you chose. Run the read-only query above again and confirm the events are still returned by the query, since the filter changes a view and not the query.

What to watch afterwards

  • A new CLSID, APPID or SID appearing in 10016 events. Microsoft's page describes the pattern as by design for Microsoft components, so a new combination is a reason to read it before assuming it is the same.
  • Failures that start when a new event pattern starts. Microsoft's page describes no failure caused by 10016, so a failure needs its own diagnosis from its own events.
  • A Windows update that adds or removes the repeating events. Microsoft's page does not say how an update changes the events.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's page is a workaround page for one event and does not list every CLSID that produces it. Its sample events come from Windows 10, Windows Server 2019 and Windows Server 2016, while the page's "Applies to" line says supported versions of Windows Client and Windows Server. It gives no steps to create the Event Viewer filter, no steps for changing DCOM permissions, and no back-out for either. Suppressing events hides information, so keep the exact values of what you suppress in your records. The wevtutil and Get-WinEvent commands only read the System log.

Sources