Event ID 5 seems to be the generic catch-all ASP error logged to the event log. There is probably a lot more out there than what we've compiled here, but hopefully the following list of symptoms / resolutions will help you.
If you are seeing the following errors:
Script Engine Exception. A ScriptEngine threw expection 'C0000005' in 'IActiveScript::SetScriptState()' from 'CActiveScriptEngine::ResetToUninitialized()' or Script Engine Exception. A ScriptEngine threw expection 'C0000005' in 'IActiveScript::Close()' from 'CActiveScriptEngine::FinalRelease()'.. or File /<file>.asp. Unexpected error. A trappable error (C0000005) occurred in an external object. The script cannot continue running. |
This is usually an access violation error, but since it's coming from a component that the error message fails to identify, the only advice I can offer is to follow a similar debugging path as the ASP 0115 error (see
Article #2171 and
KB #262187). Sometimes the error is accompanied by an Event ID 4014 error, which can often contain CLSID information that will lead you to the component causing the error (you can search for the IID / CLSID string in the registry).
Before you go the long debugging route, however, consider upgrading the server to the most recent version of MDAC (
MDAC Download Page) and the latest scripting engines (see
Microsoft Script Downloads) and reboot... and make sure your server has the latest updates (see
Article #2151). While this is not a proper, 'feel-good' debugging effort, the above steps have often resolved the problem entirely.
If you are getting an E06D7363 error in the following form:
Script Engine Exception. A ScriptEngine threw expection 'E06D7363' in 'IActiveScript::SetScriptState()' from 'CActiveScriptEngine::ResetToUninitialized()'. or Script Engine Exception. A ScriptEngine threw expection 'E06D7363' in 'IActiveScript::Close()' from 'CActiveScriptEngine::FinalRelease()'. |
Uninstall Norton CrashGuard, as it is infamous for 'inventing' errors in kernel32.dll with this error code.
If these errors are accompanied by the following ASP errors:
Active Server Pages, ASP 0241 (0x80004005) The CreateObject of '(null)' caused exception E06D7363. or Active Server Pages, ASP 0240 (0x80004005) A ScriptEngine threw expection 'C0000005' in 'IActiveScript::GetScriptState()' from 'CActiveScriptEngine::ReuseEngine()'. or Active Server Pages, ASP 0240 (0x80004005) A ScriptEngine threw expection 'C00000FD' in 'IActiveScriptParse::ParseScriptText()' from 'CActiveScriptEngine::AddScriptlet()'. or Server object, ASP 0177 (0x8007000E) Ran out of memory |
This is probably a permissions issue. Whatever these pages are trying to write to, make sure the anonymous user (IUSR_MachineName) or the authenticated user(s) have access. For example, if you are trying to create a Lotus.NotesSession object, the IUSR account needs write access to the Lotus\Notes\ folder.
If you are using Project Server, you might have the following errors:
File /<file>.asa Line <line> Out of memory. Unable to allocate required memory. and Active Server Pages, ASP 0100 (0x80004004) Unable to allocate required memory. /ProjectServer/Global.asa, line 18. |
This is often caused by global.asa being 'scanned' by Anti-virus programs and other services that might modify and/or lock various files on your server. See
KB #323019 for a description and possible workarounds.
If this error is happening from Outlook Web Access, you're probably getting one of the following errors (among others):
A Active Server control or component performed an illegal ole countinitialized call. Components used by Active Server Pages must not do this. or File /<file>.asp Unexpected error. |
You should be able to eliminate the error by reinstalling OWA and the latest Exchange service pack(s), though sometimes it may require reinstallation of IIS as well. Also, see
KB #196016 (XWEB: Outlook Web Access Fails Intermittently) and the
OWA Troubleshooting Whitepaper.
If you are getting the following error:
The description for Event ID ( 5 ) in Source ( Active Server Pages ) could not be found. It contains the following insertion string(s): File /<file>.asp Unexpected error. or File /<file>.asp Line 0 Out of memory. Unable to allocate required memory. |
One possible kludge, or at least help in narrowing down the component causing the problem, is to increase the application protection to high (isolated).
If you are getting the following error:
| Error while reading default settings. please do regsvr32 asp.dll. |
This message can be ignored (see
KB #290612), and re-registering asp.dll will probably not eliminate the error message anyway.