I have an asp.net application that incorporates vfp COM interop. The vfp mtdll consists of 1 class with 10 methods. I made the 1 class the component in a COM+ application. I have given the COM+ application the same user name and password that is running as the impersonated user in web.config. The impersonated user has full control of all data across the network. 9 of the 10 methods function flawlessly and predictably. There is however the 10th method that unpredictably causes asp.net to throw an unspecified COMException error.

The only thing suspicious about this method is that it is much beefier and slower than the other 9. It drags on while opening several tables, creating several temporary cursors and crunching data. The data is not on the web server. The data is across the network and at times takes a while to access.

Is it possible that I am having a timeout problem? How do you debug a timeout problem if COM is involved? How can I increase the time allowed that IIS5 will permit the COM object to take? Does IIS have to be configured to permit COM object methods that need more time while accessing data across the network?

Any thoughts?

Neil