Re: Event ID: 10016 // DCOM //NT AUTHORITY\NETWORK SERVICE

Chris,

You are applying the rights to the wrong object.

The SSID belongs to the IIS WAMREG admin Service. In Component Services double-click on 'Computers | My Computer' and then click on 'DCOM Config'.
From the list of objects on the right panel find the 'IIS WAMREG admin
Service' and right click, select 'Properties' and click on the 'Security' tab.

Under 'Launch and Activation permission' click on 'Edit', add the 'NETWORK SERVICE' and click on 'Local Activation' for the account.

That should do it

--
Costas


"Chris" <Chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D72596EB-0D9D-485A-AF14-3169E14A068E@xxxxxxxxxxxxxxxx
This is my second post to the group, and I appreciate all the support so far.

I have tried to google, use MSKB and this site to find a solution before
posting.

I am receiving the following error in my event log, it seems since the
installation of WSS 3.0 (side-by-side) with version 2.0.

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 13/05/2008
Time: 4:32:03 AM
User: NT AUTHORITY\NETWORK SERVICE
Computer: IBM-SERVER2
Description:
The application-specific permission settings do not grant Local Activation
permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
permission can be modified using the Component Services administrative tool.

This is what I have done so far:

1) Reviewed CLSID in Registry, LocalService is set to IISADMIN
2) Followed an article on line (silly me forgot to record #), this is the
content of the article.

Grant the correct permissions to the Network Service account
To grant the correct permissions to the Network Service account, follow
these steps: 1. Click Start, click Run, type dcomcnfg in the Open box, and
then click OK.
2. In Component Services, double-click Component Services, and then
double-click Computers.
3. Right-click My Computer, and then click Properties.
4. Click the COM Security tab.
5. In the Launch and Activation Permissions area, click Edit Default.
6. Click Add, type Network Service, and then click OK.
7. While Network Service is selected, click to select the Allow check boxes
for the following items:
• Local Launch
• Remote Launch
• Local Activation
• Remote Activation
Pressed OK twice.

I have done a reboot of the service since, as I have also updated to
Exchange SP2.

Does anyone have a further suggestion ?

Regards,
Chris

.

Relevant Pages

  • Re: Change permission remotely
    ... local administrators rights on the computers you wish to affect. ... WMI.GetStringValue HKLM, i, "ProductType", ProductType ... Sub CreateIE() ... > change permission on temp folder. ...
    (microsoft.public.scripting.vbscript)
  • Re: Move PC between domains
    ... Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA ... >> A subset of the domain (an indentified bunch of people and computers ... I think the file migration is sorted and permission issue all OK ...
    (microsoft.public.win2000.active_directory)
  • RE: Win 2000 service needs to access Win 2003 Web Server data
    ... The domain account "usr_test" has the permission of reading a log files ... However, for your application, I think if both of the two computers has one ... Microsoft Online Partner Support ...
    (microsoft.public.win32.programmer.networks)
  • Re: Joining Computers to Domain
    ... %systemroot%\debug and locate the SamOpenUser error you mentioned earlier. ... > Create a new user and delegate them the permission at the domain level. ... >> Our problem is with student admins. ... >> add computers to the domain. ...
    (microsoft.public.windows.group_policy)
  • Re: Test Your C Skills - Errors
    ... that particular character happening upon the only CPU ... instruction that locks up the CPU, ... "It is important to remember that when it comes to law, computers ... Only people can be given permission." ...
    (comp.lang.c)