Have you had DLL's fail after upgrading to 64 bit server?

Posted by quakkels on Stack Overflow See other posts from Stack Overflow or by quakkels
Published on 2010-06-15T21:33:08Z Indexed on 2010/06/15 21:42 UTC
Read the original article Hit count: 256

Filed under:
|
|
|

Hey All,

I'm wondering if anyone else has experienced failed DLL's after upgrading their servers.

My company is in the process of upgrading our code and server's after ten years of using classic ASP. We've set up our new server running Windows 2008 and IIS 7. Our classic ASP code and our new asp.net mvc code work pretty well.

Our problems started happening when we began moving our old websites to the new server. When trying to load the page on the actual server machine's browser, we initially got a 500 error. If we refreshed the page then some of the page would load but then display an error:

Server object error 'ASP 0177 : 800401f3'

Server.CreateObject Failed

/folder/scriptname.asp, line 24

800401f3

btw: On remote machines we would just get 500 errors.

Line 24 is the first executable code in the script:

'23 lines of comments

set A0SQL_DATA = server.createobject("olddllname.Data")

'the rest of the script

That specific line is trying to use a ten year old DLL to create a server object. I don't think the server configuration is a problem because I'm able to create "adodb.recordset" server objects without any problems.

Is there an issue when running correctly registered old DLL's on 64 bit systems?

Is there a way to get old DLL's working on 64 bit systems?

© Stack Overflow or respective owner

Related posts about ASP.NET

Related posts about dll