Randomly C0000005 errors

[aa]

Several times pr week, IIS crashes, and logs error messages to the event log
like this:

Script Engine Exception. A ScriptEngine threw expection 'C0000005' in
'IActiveScript::SetScriptState()' from
'CActiveScriptEngine::ResetToUninitialized()'..
A trappable error (C0000005) occurred in an external object. The script
cannot continue running..

Script Engine Exception. A ScriptEngine threw expection 'C0000005' in
'IActiveScriptParse::ParseScriptText()' from
'CActiveScriptEngine::AddScriptlet()'..

When it occurs, IIS must be restarted to work again. The application is a
"standard" ASP web application, and uses VB/C++ COM-components to connect to
a Oracle database. It runs on W2K, IIS 5

Anyone had the same error messages (and solution)?

Best regards,

Eivind Eriksen

[Aaron Bertrand [MVP]]

http://www.aspfaq.com/2355
http://www.aspfaq.com/2171

<aa> wrote in message news:#zO5D1#VCHA.3740@tkmsftngp08...

[Pat]

This is actually caused by corruption of TLS (Thread Local Storage). What
happens is an ASP page that runs a COM object that utilizes TLS fails, and
the thread is returned to the ASP pool. When the thread gets recycled, then
this failure is thrown. Upgrade to the latest MDAC (www.microsoft.com/data)
and see if the issue goes away (MDAC uses TLS). You should also be on the
latest scripting engine (msdn.microsoft.com/scripting). If it doesn't, then
this will require a fairly invasive debugging session.

Basically, you have to attach a debugger and catch every exception. Trace
them to a log file and wait for this stack. Then go back until you find the
previous failure on the same thread in the log file. That is the
misbehaving component. Upgrading MDAC/VBScript is way easier.

Pat

"Aaron Bertrand [MVP]" <aaronATaspfaq.com> wrote in message
news:e$FZGz$VCHA.3764@tkmsftngp08...

[Eivind Eriksen]

Updated MDAC to 2.7 Refresh, and Scripting to 5.6 one week ago. No more
crashes has occured after that. But, there is much lower traffic at the
website now, than it was before the update. The server has peak periods 6
times a year when customers registers their power meter readings, and now I
think I have to wait for the next peak period to ensure that the update
solved the problem.

Thank you so far
Eivind Eriksen

"Aaron Bertrand [MVP]" <aaronATaspfaq.com> wrote in message
news:e$FZGz$VCHA.3764@tkmsftngp08...