>Yes we used DCOMCNFG to provide NETWORK SERVICE with access to the COM file. This produced a slightly different result. Whereas before the failure and error message was immediate, now the website/browser seems to hang for a minute or so before it reports the same error. IE Cannot create ActiveX object. Further digging shows that the reason is a timeout waiting for the COM to report back that it had started. Here is the frontend of the code. Do you see anything that might be producing the problem? Remember it works fine in the Cassini environment.

Are you seeing anything in your log file? One thing I sometimes do is to add a one liner to the Init() just to make sure COM instanciation is even completing, ex:

STRTOFILE(TRANSFORM(DATETIME()) + " : Started", "C:\SomePath\Test.log")
RETURN

Then I'll make sure both ASP.NET and the COM component have access to that path and run your code. If the log file is written you know that the interop stuff is working OK, it's probably a permission issue.

I also tend to move code out of the Init() and into another method (ex. Setup()). This lets me do things like the paths in the properties before that code runs. I instanciate the object, set the properties, then call Setup().

One thing to be aware of - you're probably not sitting in the directory you think you are in the Init() - that could be why it's failing.

Take a look at this post by Rick Strahl re: debugging your VFP COM component - it can definitely help to be able to trace through the code:

http://www.west-wind.com/weblog/posts/170736.aspx