Hi Chinmay,

In response to FoxISAPI parts, you are correct with
MyExe.MyMethod.MyClass


I have found that the CoCreateInstance() error is typically associated with either actual errors when trying to create your COM server class, or user rights via DCOM are preventing access.

If there Time-out on CoCreate via the DCOM access, I found that typically to follow would be a message from the USER32.dll, but it has its own time-out delay. You may need to check the DCOM settings / access / priviledges and then retry.

But, before that, make sure your COM server can be loaded without error. Also, there cant be any user-interface activity, wait windows, dialog boxes to "find a file" that the COM server is trying to open, etc... One other special note about invoking a COM server. If your app is in a directory such as C:\MyWork\WebApps\TestCOM, that IS NOT the actual default directory that the COM server will be started in... it will be started in C:\ so you may have to force a pathing default when your COM server initially starts up.

Also, have you considered any other web-based frameworks that are available? Such as DVRWeb in the downloads section, Web-Connection, ActiveVFP, etc???

HTH,

Don