I'm trying to execute classic ASP pages on a windows 2008 64 bit R2 box.
Initially the problem was with registering dlls : That's now fixed. Register DLL file on Windows Server 2008 R2
Now when I try to access the page I get this error
Active Server Pages error 'ASP 0241'
CreateObject Exception
index.asp
The CreateObject of '(null)' caused exception C0000005.
Server object error 'ASP 0177 : c0000005'
When I change the code from Server.CreateObject to CreateObject .. I end up with this error
Active Server Pages error 'ASP 0115' Unexpected error index.asp
A trappable error (C0000005) occurred in an external object. The script cannot continue running.
I checked everything I could - Access and admin rights etc. The application pool are set to No Managed Code + Classic mode.
Any ideas to fix this?
You're not going to fix this in ASP. The C0000005 is the Access Violation Exception. This occurs when code attempts to read memory that it hasn't allocated.
The dll is doing something bad when it loads or during the construction of the object.
Have you tested the dll with a simple .vbs file?
I had exactly the same error.
In my case the C0000005 error was caused by a missing dependancy.
ProcessMonitor help me finding it. (Filter by process, and check "Name not found")
Copying the needed file in the right place solved my problem. (In my case VB6FR.dll was a needed dependancy for vb6 in french.)
I spent several hours chasing this down as well.
In my case, it was caused by reusing a recordset object several times without closing it between DB calls. The code was working without apparent issue in several similar instances, and then one of them just stopped tolerating the process.
The error occurred when I attempted to close the recordset at the end of the page, which made troubleshooting more difficult.
I cleaned up the code, ensuring the recordset was closed between calls, and this resolved the issue.
I had same error while loading the csv file data more than once. Step 1 - Firstly create a temp table to transfer the csv data into temp table and then move to main table and delete temp table once data is moved. This has to be done programmatically.
Step 2 - Go to mysql and select the database and use this query ( SHOW FULL PROCESSLIST; ) use without brakets. this will show you status of running objects.If you find any object with status as "Sleep" this needs to be cleared before 2nd attempt to upload the file. usually the default wait time is about 28000 sec. You need to reduce it as per requirement. Code to reduce the wait time is ( SET GLOBAL wait_timeout=5; ). Use without brakets. Use this is mysql. this will re-set your global wait time to 5 sec, (change as per your needs). This should resolve your problem. All the best.
I had the same problem happen sometime after KB4093114 was installed on a server. (I'm not 100% sure that the KB caused the problem but I suspect so because the scripting engine was updated.)
The problem was caused by a recordset that output a varchar(max) field to the markup. Even though the error does not provide a line number, I was able to pinpoint it to the outputting of the varchar(max) field through trial and error.
<%
...
rs.Open "SELECT LongDescription FROM Table1"
while (not rs.EOF)
%> <p><%= rs("LongDescription") %></p> <% ' ERROR HAPPENS BECAUSE OF THIS LINE
rs.MoveNext
wend
%>
Removing that line fixes the problem. Also, casting the field to a non-max varchar also fixes it:
rs.Open "SELECT LongDescription = Cast(LongDescription as varchar(4000)) FROM Table1"
To make matters worse, I found that once the error happens, even if you fix it you need to recycle the app pool to make the error go away.
For my experience, you are using AVG Free, and after an update, you got this kind of error.
Just ran into this same error while trying to use my own com control and in my case it turned out to be caused by my dll being compiled in debug mode.
There are two ways around that:
Run IIS in debug mode. For 32 bit you use the following line: C:\Windows\SysWOW64\inetsrv>w3wp.exe -debug
Note that you have to stop the IIS service and for 64 bit you use the one in System32.
Compile a release version :)
I'm running some very old ASP code in IIS on a new Windows 10 1803 installation, and had it briefly running correctly then started to get this error message after running a repair in Office to fix an Outlook issue.
In this case, reinstalling the Microsoft Access Database Engine fixed the problem.
You might want to check out this blog entry, titled "Classic ASP (ASP 3.0) doesn’t work on 64bit with 32bit COM objects" http://blogs.msdn.com/b/robgruen/archive/2005/05/26/422328.aspx
it's a bit dated and the author incorrectly refers to the ASP handler as an ISAPI filter (it's an extension, not a filter), but otherwise the information seems good.
if the asp handler is only compiled as 64bit, you will not be able to load a 32bit COM object into it no matter what you do.
the author does mention something about a COM+ solution. I have a feeling that a 32bit out of process COM+ package would be able to load this 32bit COM object and your ASP page could make cross process calls to this COM+ package.
good luck, Mark
来源：https://stackoverflow.com/questions/4649487/classic-asp-c0000005-error-on-execution