David,

Exactly where do you set the DCOM Launch Permission? They changed this stuff in WIN2003. We have set a Local Security Policy for DCOM Launch, but that only solves the launch problem on a logoff.

Thanks for your help on this. This is THE last issue for us to resolve before a production roll-out.


>Jeff,
>
>>We are having a problem figuring out how to configure a COM server / DCOM to accept client launchs after a WIN2003 system reboot.
>>
>>As is stands now, if the box is bounced, a login is required followed by a manual restart of the COM server in the Component Services console.
>
>Perhaps your DCOM Launch Permission is set to "Interactive" user? Better to set it to a specific user account that has been given proper permissions to run the server and access the data. Interactive requires that someone be logged in on the server.