On a new server install, I am able to run my WWC app as a File mechanism. However, if I turn it to automation, I can't make it run at all. Basically, in the Task Manager, the EXE is now showing in the process list. After the browser timeout, the WWC error txt log file will add an entry about timeout being applied. I can create my WWC app COM object from VFP. It creates ok. I know the problem relies at the access level. From DCOMCNFG, I have the same setting as usual which is to run the COM object with the Identity being set to the administrative account. Presently, there is only one account and that is the one being used for the test environment. I also, in the main DCOMCFNG setting, for the rights, have defined the administrator, the LWAM and LUSR accounts in it for the access list. So, the access list is as before on all other setups I have done. However, in this case, the administrator account defined for my COM object doesn't seem to kick in.

The test server is not defined as a domain. So, when I select the administrator account from Identity, it shows properly the PC name\administrator.

My COM object is also registered with the MyApp.exe /regserver. I know it is probably a simple issue. But, I can't seem to find what it is.