Hi,

Try to deploy a wconnect app to Windows 10 machine. It works under "File" mode. In "COM" mode, it only works when I set DCOM identity to "The interactive user", with two server instance showing. But when I set to "The launching user", the request times out... The app pool in IIS is "local system".

Anyone knows why this is happening (or not happening)?

Thanks in advance!

Jun

Hmmm... that should work assuming the Application Pool is actually running under SYSTEM.

You can double check - go to the Module Administration Page and check the bottom of the page for the account your App Pool is running under:

This should say SYSTEM or YOURMACHINE$ (which is NETWORK SERVICE).

If that's not it, then the problem most likely is that your application is trying to start but failing.

Also make sure you enable Unattended mode in your YourApp.ini server startup file.

Unattendedcommode=On

Make sure you can instanatiate the COM object from FoxPro and launch that way. Otherwise look for wctrace.txt in the startup folder. If you're using a Web Connection 6.18 server startup failures (other than hangs which is the most likely issue) should display an error page on the first hit if there is a problem in the OnLoad() startup code.

If all that still fails add trace commands to your startup code:

FUNCTION OnLoad()

this.Trace("OnLoad Fired")

... your other code

this.Trace("Doing some processing...")

... your other code 

this.Trace("OnLoad Completed")
ENDFUNC

Compile and run that then check your wctracelog.txt file in the startup folder. Make sure the Application Pool user has rights to write files there...

+++ Rick ---

Thanks Rick!

It was "Unattendedcommode" thing, all good and running now! We are migrating an old app from 4.68 to 6.18. The whole process is relatively smooth thanks to the excellent documentation on this very subject. Again, thank you for providing such a wonderful product! Now off to implementing new REST API project...

Jun

Thank you for the kind words on the docs.

I've also updated this topic in the documentation:

• Dealing with COM Server Startup Issues

+++ Rick ---