But it could also be something like “Network service” or “Local service”.Ĭlick the name that applies to you, and then click the appropriate permission. In my case, it was “ SYSTEM” needing “ Local Activation” permissions. In Step 1, you also wrote down the account that caused the error, and the needed action to fix event id 10016. If you had an error related to “do not grant Access permissions”, you would typically choose “ Access Permissions” -> Customize, and then click Edit… In my case, I had issues with Local Activation, so I choose “ Launch and Activation Permissions” set to Customize, and then click Edit… If you followed my steps, you have written it down at Step 1 Right click the application name and click Properties If you followed my instructions, you wrote the name down at Step 3. Now, scroll down to the application you have issues with. Navigate to Component Services -> Computers -> My computer -> DCOM Config.
The following steps will solve your error.Ĭlick Start, type “ Component Services“, rightclick Component Services and click “ Run as administrator” In my example, the id’s are:ĬLSID : ” window, select the Computername\Administrators and then activate the “Full Permissions” checkbox.Īlmost there! We now have set all permissions to actually change the Local Activiation settings. Open your event viewer, and make note of the ID’s. Just make sure you have an Administrator account on your pc and you’re good to go! :-) Times have not changed since then: it’s still a hell of a job to fix event id 10016. Well, that reminds me of an old blog post of me, back in 2010. This security permission can be modified using the Component Services administrative tool. To the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (via LRPC) running in the application container not available SID. The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
#Adobe digital editions unknown permission error windows 10#
On a Windows 10 machine, you may encounter Event ID 10016 in your eventlog:
0 kommentar(er)
