I'm having a nasty little problem that I am hoping has an easy answer.
there are two places on the web site where on average 350 items are added or updated.
When any of these two actions occur, for 3 - 5+ seconds, the CPU usage on the server is pegged at 100%, and the database is locked for that entire period. Then, if nobody else is using the database or ordering platform, it will continue as normal.
If, however, a read/write request is made to any database during this 3 - 5 second window, the server then freezes all ASP activity on every web site its hosting for at least 2 minutes. Eventually it works itself free, but
by that time its too late.
I was able to get the error the users were having..
Active Server Pages error 'ASP 0113'
Script timed out
The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools.
This code worked fine before, not sure what's going on now.