Question

我们在Classic ASP上编写了一个非常古老的遗留应用程序。最近在几台服务器上我们开始出现致命错误。 IIS进程崩溃。我们使用IIS调试工具获得了很少的错误堆栈跟踪。有两种常见的错误类型。

我们在应用程序中只使用了几种类型的COM组件：ADO，Scripting.Dictionary，Scripting.FileSystem＆amp; MSXML6。

IIS日志说错误描述是访问冲突异常（0xC0000005）。

您对错误原因或未来调试方法有任何想法吗？任何获取有关此错误的更多信息的方法都将非常受欢迎。

感谢。

堆栈跟踪：

1。的

1996e18
oleaut32!VariantCopy+173
oleaut32!SafeArrayCopyData+14e
oleaut32!SafeArrayCopy+e3
oleaut32!VariantCopy+5b
oleaut32!VariantCopyInd+1a1
asp!CComponentObject::GetVariant+27
asp!CApplnVariants::get_Item+da
oleaut32!DispCallFunc+16a
oleaut32!CTypeInfo2::Invoke+234
asp!CDispatchImpl<IVariantDictionary>::Invoke+55
oleaut32!CTypeInfo2::Invoke+58a
asp!CDispatchImpl<IApplicationObject>::Invoke+55
vbscript!IDispatchInvoke2+b2
vbscript!IDispatchInvoke+59
vbscript!InvokeDispatch+13a
vbscript!InvokeByName+42
vbscript!CScriptRuntime::RunNoEH+22b2
vbscript!CScriptRuntime::Run+62
vbscript!CScriptEntryPoint::Call+51
vbscript!CSession::Execute+c8
vbscript!COleScript::ExecutePendingScripts+144
vbscript!COleScript::SetScriptState+14d
asp!CActiveScriptEngine::TryCall+19
asp!CActiveScriptEngine::Call+31
asp!CallScriptFunctionOfEngine+5b
asp!ExecuteRequest+17e
asp!Execute+24c
asp!CHitObj::ExecuteChildRequest+12c
asp!CErrInfo::LogCustomErrortoBrowser+28a
asp!CErrInfo::LogErrortoBrowserWrapper+8b
asp!CErrInfo::LogError+77
asp!HandleError+100
asp!HandleErrorMissingFilename+ac
asp!CActiveScriptEngine::Call+a7
asp!CallScriptFunctionOfEngine+5b
asp!ExecuteRequest+17e
asp!Execute+24c
asp!CHitObj::ViperAsyncCallback+3f0
asp!CViperAsyncRequest::OnCall+92
comsvcs!CSTAActivityWork::STAActivityWorkHelper+32
ole32!EnterForCallback+c4
ole32!SwitchForCallback+1a3
ole32!PerformCallback+54
ole32!CObjectContext::InternalContextCallback+159
ole32!CObjectContext::DoCallback+1c
comsvcs!CSTAActivityWork::DoWork+12d
comsvcs!CSTAThread::DoWork+18
comsvcs!CSTAThread::ProcessQueueWork+37
comsvcs!CSTAThread::WorkerLoop+190
msvcrt!_endthreadex+a3
kernel32!BaseThreadStart+34

2。的

scrrun!FreeList+f   
scrrun!VBADictionary::~VBADictionary+28   
scrrun!VBADictionary::`scalar deleting destructor'+d   
scrrun!VBADictionary::Release+17   
oleaut32!VariantClear+b1   
oleaut32!ReleaseResources+98   
oleaut32!_SafeArrayDestroyData+4d   
oleaut32!_SafeArrayDestroy+b3   
oleaut32!SafeArrayDestroy+f   
oleaut32!VariantClear+75   
vbscript!VAR::Clear+a6   
vbscript!CScriptRuntime::Cleanup+63   
vbscript!CScriptRuntime::Run+8d  
vbscript!CScriptEntryPoint::Call+51  
vbscript!CScriptRuntime::RunNoEH+1e02 
vbscript!CScriptRuntime::Run+62  
vbscript!CScriptEntryPoint::Call+51   
vbscript!CScriptRuntime::RunNoEH+1e02  
vbscript!CScriptRuntime::Run+62   
vbscript!CScriptEntryPoint::Call+51   
vbscript!CScriptRuntime::RunNoEH+1e02   
vbscript!CScriptRuntime::Run+62   
vbscript!CScriptEntryPoint::Call+51   
vbscript!CScriptRuntime::RunNoEH+1e02   
vbscript!CScriptRuntime::Run+62   
vbscript!CScriptEntryPoint::Call+51   
vbscript!CSession::Execute+c8  
vbscript!COleScript::ExecutePendingScripts+144  
vbscript!COleScript::SetScriptState+14d  
asp!CActiveScriptEngine::TryCall+19   
asp!CActiveScriptEngine::Call+31   
asp!CallScriptFunctionOfEngine+5b   
asp!ExecuteRequest+17e  
asp!Execute+24c   
asp!CHitObj::ViperAsyncCallback+3f0   
asp!CViperAsyncRequest::OnCall+92   
comsvcs!CSTAActivityWork::STAActivityWorkHelper+32   
ole32!EnterForCallback+c4   
ole32!SwitchForCallback+1a3   
ole32!PerformCallback+54   
ole32!CObjectContext::InternalContextCallback+159   
ole32!CObjectContext::DoCallback+1c   
comsvcs!CSTAActivityWork::DoWork+12d   
comsvcs!CSTAThread::DoWork+18   
comsvcs!CSTAThread::ProcessQueueWork+37   
comsvcs!CSTAThread::WorkerLoop+190   
msvcrt!_endthreadex+a3
kernel32!BaseThreadStart+34

Answer 1

过去几周我们的情况非常相似。追踪这个问题非常复杂。问题出在VB6代码的OnError处理程序中。有两种情况需要重现：

您没有OnError处理程序，发生错误并直接转到 IIS
在OnError处理程序中发生错误并直接转到IIS。

大约100次此类错误后，IIS将无法正常工作。在这一刻之后，这将是绝对不可预测的行为。

可捕获的错误0xC0000005

1 个答案: