I posted this message a while back which resulted in having to deal with a related issue before it could be determined if it was causing my original problem which, as it turns out, is still occurring.

I have a small VFP COM Server running under FOXISAPI and IIS4 on an Intranet here. It may eventually be moved over to a production web server, but right now it is running on what is essentially a workstation level machine. This is an Intranet scenario being utilized for the in-house computer technicians and administrators so there is not high volume traffic. I have seen several times when a web hit would produce a timeout even tho no one else was hitting the web server, as if it was just locked up. Both of the available COM server instances were currently in memory. But I had to clear them using Task Manager as FOXISAPI/Reset would not fire. It seems there must be something amiss in a configuration setting or settings somewhere. I have had to at least once use the Kill utility to shutdown the IIS service and restart it when manually clearing the COM servers using Task Manager was not sufficient. Has anyone else seen this type of problem using VFP COM servers and FoxIsapi?

Machine Data:
PIII, single processor, 128MB RAM, 8GB SCSI hard drive, 128 MB swap file.

FOXISAPI Data:
Allowing 2 instances of the COM server, busytimeout = 30, releasetimeout=25

Thanks,
Bill