>Thanks for the ideas, unfortunately I've already tried most of them...
>
>I agree that things USUALLY have a logical explanation if a reboot doesn't correct it but not this time for me.
>
>We have tried several reboots, querying data on the server and across the network. No configuration changes were made to IIS or WinNT. No code chages were made immediately before the change.
>
>We tried setting up another Web Server from scratch (formatting, loading NT, IIS, Service packs, Option pack 4.0, ADO 2.5, set everything up, etc.) and it was working fine until it was put into production and then it began doing the same exact thing - unusably slow ASP/COM data access - FOXISAPI apps run great. But it is running different versions of ADO, VFPODBC, service pack 5 instead of 4.
>
>I just tried it on another server box (luckily we have enough machines lying around) set up from scratch but only loaded 2 of the ASP/COM apps and so far it is running okay. We will slowly add the other apps on (every few days) doing image backups after each until/unless the slowness starts up again and won't go away. Hopefully this will isolate it to a particular app that is starting the problem and give up the ability to quickly recover the system back to a working point with a restore.
>
>Any other ideas would be appreciated...
>
> ...Scott

The last edition of MSDN magazine had an excellent article on stress testing that gives you some tips on what to monitor to fine tune IIS. www.msdn.microsoft.com/voices/news