pbunyon

I recieve the following:

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{BC866CF2-5486-41F7-B46B-9AA49CF3EBB1}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19). This security permission can be modified using the Component Services administrative tool.

Upon clicking link and attempting to fix per:
Using Regedit, navigate to the following registry value HKCR\Clsid\clsid value\localserver32
My reg stops at HKEY_CLASSES_ROOT\CLSID and no Clsid\clsid value\localserver32.



Re: Windows Desktop Search Help DCOM 10016 Fix?

rivet

I didn't write this, I found it elsewhere. Hasn't worked for me, but perhaps you'll have better luck. Please note, the example below is not the exact same SID as yours, but the path to tracking it is hopefully identical.

The COM Server application with CLSID has to be tracked down in the registry, in this case the following reg key;
HKEY_CLASSES_ROOT\CLSID\{BA126AD1-2166-11D1-B1D0-00805FC1270E}


In this key you can acquire the AppID, in this case the following AppID;
{27AF75ED-20D9-11D1-B1CE-00805FC1270E}


The AppID has to be tracked down in the registry, in this case the following reg key;
HKEY_CLASSES_ROOT\AppID\{27AF75ED-20D9-11D1-B1CE-00805FC1270E}


In this key you can acquire the LocalService name, in the case the following name;
Netman


The LocalService has to be tracked down in the Component Services MMC; in this case Netman is listed within the DCOM Config section.


Browse to the Security Tab, edit the Launch and Activation Permissions, and make necessary changes. In the case, NETWORK SERVICE needed to be added with Remote Launch and Remote Activation permissions.




Re: Windows Desktop Search Help DCOM 10016 Fix?

TedSA

|This worked fiine for me.

In my case the VMM Beta 2 service running on one server was trying to get access to the virtual server service on a different server and it was generating the DCOM 10016 event described by the first post on this thread, albeit with different SIDs.

The sequence of steps described in the 2nd post led me to NetMon just as described and from there I was able to modify the security settings to give the VMM server the access it needed.

Thanks.