Don
I think it's more the second reason that you named. In fact, there was a power problem that disconnected this server and when i switched it back on, this problem started to appear. Since this web service is really important and gives support to many sites and B2B applications, i just reformated to server, installed Win2K, and installed in it my web services. While i was at it, i also 'upgraded' them to COM+, and all is well now.
Check out what i noticed: reformating the server and installing Win2K: 90 minutes. Installing IIS and finishing definitions: 30 minutes. Rebuilding all VFP Web Services and making them COM+: 5 minutes :-)
BTW, ASP listener is way much slower than isapi ( i had to use asp at the beginning with Win2k until i fixed isapi ).

Thanks for your help

>Not running as a SOAP option, but I've seen similar when running ISPAI (originating from FoxISAPI) and found it to be one of 2 things.
>
>1. Security rights / access / directory / launch priviledges. If the DCOM Configuration has had changes since the program recompile and changed something (...no VFP change something in an existing registry entry??? :) it may need to be just edited and resaved.
>
>2. The other option is that the ISAPI crashed internally for some strange reason and couldn't get a valid handle to the object it WAS pointing to -- or extra instances were created and has become confused.
>
>HTH