Classic ASP application not working on IIS 7with windows server 2008

Question

I have an old classic ASP application which runs fine on xp and windows 7 too.. but when I deploy the application on windows servre 2008 32 bit with ii7 installed on it, it gives following error

Active Server Pages error 'ASP 0241'

CreateObject Exception

/ncrimageviewer/batch_children.asp

The CreateObject of '(null)' caused exception C0000005.

Server object error 'ASP 0177 : c0000005'

Server.CreateObject Failed

/ncrimageviewer/batch_children.asp, line 497

c0000005

event viewer shows

Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919413, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x023d0068, process id 0x17fc, application start time 0x01ccbfc10d1ea3ff.

and

Error: File XXXX.asp CreateObject Exception. The CreateObject of '(null)' caused exception C0000005..

In my code I am loading the custom dll using server.createobject..

I am searching internet since yesterday but have not found any solution.

I have tried both classic and integrated application pool. Also tried "no managed" option

I given the read/execute permission to to c:\ipubnet\wwwroot directory for "Network services" and "IIS_IUSERS"

I also ran process monitor but didnt find any "denied" status.. there were bunch of "buffer overflow", "Name not found" and some "FILE LOCKED WITH ONLY READERS" but i have no idea what they mean..

I find in google that there was mdac bug which caused the access violation error, but i think in windows 2008 that should be corrected as that bug is very old.

Do I need to update mdac(or wdac?) on server 2008?

Guys please help me out here on how to solve the problem as I am not much of ASP guy..

Answer 1

I am not sure the problem is with ASP. The C0000005 is the Access Violation Exception. This occurs when the code attempts to read memory that hasn't been allocated and would suggest a problem with the DLL.

I would try creating a simple .vbs file that calls the custom DLL to see if the DLL is the problem. I am not sure what the custom DLL is doing, but my guess is it may depend on something not available in Windows Server 2008.