As long as you're not using the same COM object Web Connection isn't going to care about anything else running on the same machine. Nor would FoxISAPI. Both are routing through separate ISAPI extensions.

One thing that could be a problem is that FoxISAPI is doing CoCreateInstance calls and not cleaning them up. Actually, Web Connection used to do that as well, but more recently Web Connection no longer makes CoCreateInstance calls in IIS as IIS already has the COM runtimes loaded.

However, that issue wouldn't cause crashes, but it could result in servers that won't unload.

+++ Rick ---

>A few months back I was attempting to setup a foxISAPI project on a laptop. The laptop had WWC and some "docking" services for plugging into the office server.
>
>There were "Cocreateinstance" errors driving the foxISAPI COM, but, foxISAPI would respond to a reset. If recollection serves, a folder that the foxISAPI COM directed it's INI files to, was missing.
>
>That was probably the problem - but any info related to issues running a foxISAPI service next to a westwind service or a "connection" (docking) service would be appreciated.
>
>Thanks