Re: Remote launch fails with E_ACCESSDENIED

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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

  • Remote control over a XP Pro RDP session after installing SP2
    ... Before installing SP2 on a XP Pro client, I was able to monitor a remote RDP ... session from another session on a 2003 Server. ...
    (microsoft.public.windowsxp.help_and_support)
  • After Office XP SP3 installed - intermitent problems with forms
    ... 2000 server Sp1 for the past year with absolutely no ... After Sp3 installed we understandably get the 'a program ... I have returned our clients to SP2 by reloading Outlook ...
    (microsoft.public.outlook.program_vba)
  • Object DCOM access SBS2003
    ... I have a Third Part System installed in my SBS Windows 2003 Server SP1 and I ... It give me an error in this third part system's client just like Access ... This third part system has its access comes by the DCOM object so I already ...
    (microsoft.public.windows.server.sbs)
  • Access DCOM remotly W2003
    ... I have a Third Part System installed in my SBS Windows 2003 Server SP1 and I ... It give me an error in this third part system's client just like Access ... This third part system has its access comes by the DCOM object so I already ...
    (microsoft.public.security)
  • Re: FIPS and Remote Desktop
    ... workstations all run XP SP2. ... Now Remote Desktop Connecitons longer work. ... but XP SP2 does support FIPS compliant ...
    (microsoft.public.windows.terminal_services)