Forum Moderators: phranque
It is slightly irritating knowing that it exist on your logfile but search result never produced a meaningful meanings.
Only example I had was to close all your asp objects like recordsets etc.
Can anybody perhaps explain a better way then one search result? Funny enough Microsoft site didnot produced I think any results!
Much appricated.
Bravo
Look at which pages it's happening on and try to work out which of these three reasons could be appropriate;
1) Your ASP code caused the error as part of an otherwise normal operation.
2) The browser responded in an unexpected way and provoked an error in your ASP code.
3) The ASP engine has crashed.
The third option seems to be pretty prevalent on cheaper shared hosting where one badly coded site can bring down the ASP engine for everyone else. These are the errors that just happen randomly and you can't replicated even with the exact same data. Typically engine crashes are down to memory leaks from objects not being destroyed.
The other options are really candidates for better error trapping / data parsing in your own code so that if something does go wrong you can handle it gracefully.
You also might want to try replicating their actions using the data in your log to see if you can provoke the same error.
- Tony
Most grateful.
Bravo
