Re: Remote launch fails with E_ACCESSDENIED

Hey! These registry entries were not present but were re-added someow while
I was testing one of the servers that fails:

HKCR\AppID\<clsid>
HCKR\CLSID\<clsid>\AppID

This registry entries was not and is still not present:

HKCR\AppID\<exe>\

Perhaps I should try restarting the DCOM Process Launcher service, but this
seems to require a reboot.

Paul

"Paul Baker [MVP, Windows Desktop Experience]"
<paulrichardbaker@xxxxxxxxxxxxxxxx> wrote in message
news:OpGdwStqIHA.3408@xxxxxxxxxxxxxxxxxxxxxxx
The user is not a member of the "Distributed COM Users" group, but they
are a member of the "Administrators" group, which does give them remote
launch, activation and access permissions.

Today, it is working for some reason. I tried it again just to be sure
where I was at. But it is not working on three similar servers. I did find
AppID related registry entries I thought I had deleted. I made sure to
delete them all from all servers. I wonder if that is something to do with
it. Maybe I need to restart a service for it to take effect.

HKCR\AppID\<clsid>
HKCR\AppID\<exe>\
HCKR\CLSID\<clsid>\AppID

Paul

"Brian Muth" <bmuth@xxxxxxxx> wrote in message
news:OPKCr8jqIHA.1316@xxxxxxxxxxxxxxxxxxxxxxx
If I understand you correctly, you have found that if the client is Win
2003 Server SP1 and the server is Win XP SP2, the remote object is
successfully instantiated. However the reverse (where the client is WIn
XP SP2 and the server is Win 2003 Server SP1) you get an access denied.

Sanity check:

Is the user a member of the "Distributed DCOM Users" group? Using
Component Services, right-click on "My Computer", "Properties", "COM
Security", and check the Access and Launch Permissions.






.

Relevant Pages

  • Re: cleaning unwanted COM objects out of registry
    ... >Usually COM servers should remove their registry entries themselves (and ... >those built with ATL usually can do so). ... >COM DLLs from your harddisk without unregistering them with "REGSVR32 /u ...
    (microsoft.public.vc.atl)
  • Re: cleaning unwanted COM objects out of registry
    ... >>> Short of manually editing the registry, how can I get rid of the ... >>> unwanted controls? ... >>Usually COM servers should remove their registry entries themselves (and ...
    (microsoft.public.vc.atl)
  • Re: Migration EXC 2003 to 2007
    ... it's not said that you can launch it after setp has been completed. ... What is best reinstall Exchange 2K7 after remove it (i do not have any ... I added our admins group there and the 2K3 exchange servers in the ...
    (microsoft.public.exchange.setup)
  • Re: Migration EXC 2003 to 2007
    ... that we can launch it after domain prep has already been launched but it's not said that you can launch it after setp has been completed. ... the OU has been created and the exchange organisations admins were empty and exchange servers only contained the 2K7 server. ... exchange 2007 there was new OU created called MSExchange Security Group and it has the following in there: ...
    (microsoft.public.exchange.setup)
  • Re: Available memory and limit on thread creation
    ... The target production servers are much larger than my test system. ... using native methods for my client socket threads doing socket IO. ... launch means more servers in the farm. ... > The work packets must decide co-operatively when they have done enough ...
    (comp.lang.java.programmer)