Jeff,

>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.

You can always get to DCOM settings by going to the Start->Run dialog and typing DCOMCNFG. That will bring up Component Services, and you can drill down into Component Services -> Computers -> My Computer -> DCOM Config.

However, if you are running this as a COM+ Application, you would go into the COM+ Applications node instead. Either way, you want the Identity Tab to set the account used for running the server (a change from Interactive to a specific user account is what I was suggesting).

If configuring with DCOMCNFG, the Security tab is where you would give the specific account launch permission, although in COM+ Applications that might be a little different (it's been a while since I've completely configured one both ways -- inside and outside of COM+).

Bottom line: You've got a combination of giving a specific user account the Launch Permission (at least for DCOMCNFG situations) AND setting the Identity to that specific user account. My experience with DCOMCNFG was mostly with running Web Connection in COM mode, where the hit from web page, coming in through Rick's wc.dll could auto-start the EXE even with no one logged in on the computer -- but NOT if you had its identity set to Interactive.

Although not a complete answer, maybe this will give you a shove in the right direction.