Classic ASP : C0000005 Error on execution

前端 未结 10 821
旧巷少年郎
旧巷少年郎 2020-12-03 22:00

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 W

相关标签:
10条回答
  • 2020-12-03 22:51

    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:

    1. 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.

    2. Compile a release version :)

    0 讨论(0)
  • 2020-12-03 22:54

    For my experience, you are using AVG Free, and after an update, you got this kind of error.

    0 讨论(0)
  • 2020-12-03 22:54

    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

    0 讨论(0)
  • 2020-12-03 22:59

    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.

    0 讨论(0)
提交回复
热议问题