Techy webdev localhost problem

Dimrill · **Posted:** Tue Nov 17, 2009 17:25

I code my webshite in classic ASP. Yes, I know, shut up. For the last tumpty tum years I've used a virtual drive under IIS to have a local copy to test stuff out on using http://localhost/dim. All's worked fine and dandy until I've installed Windows 7 64-bit. Since: heartache and headache.

Since then I've been unable to use my local copy due to the error:

Quote:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

/dim/index.asp, line 65

That line is my connection string to the access database behind my site

Quote:

strconn = "DRIVER={Microsoft Access Driver (*.mdb)};DBQ=" & Server.MapPath(MY FACKING DATABASE NAME)
set conn = server.createobject("adodb.connection")
conn.open strconn

where it falls over. From searching around the problem lies with the Windows 7 64bit ODBC. Hilariously (!), there are two consoles for this both called the same name.

Quote:

* The 32-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\SysWoW64 folder.
* The 64-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\System32 folder.

The first one is what the control panel link goes to, the second you have to navigate to and run from there. The problim: The 64bit ODBC will not link to anything from Firefox. The DSNs listed, of which there are three, all give me an error when trying to remove or edit them. :'(

The 32-bit ODBC is all set up correctly and all the DSNs listed (about twenty two billion) all allow me to edit to my heart's content. But Firefox or IE won't seem to use the 32-bit version instead of the 64-bit one.

I've tried altering the connection string to no avail. I've tried transferring everything into a MySQL database to no avail. I'm at my wits end with it. How the hell can I force Firefox or IIS, even, to use the 32 bit ODBC?! Man hug for the victor who can point me in the correct direction.

Cras · **Joined:** 30th Mar, 2008 **Posts:** 49244

Launching a DSN shouldn't use ODBCAD32.exe at all - it's the administration console, and has nothing to do with actually making the connection, which I assume is your issue. I would hazard a guess that the actual ODBC drivers odbc32.dll etc are the ones causing you the problem.

Suggestions:
Unregister all the 64-bit dlls using regsrv32 -u and see if that does anything
Stop using DSNs - use OLEDB via a direct connectionstring instead.

Dimrill · **Posted:** Tue Nov 17, 2009 17:36

HAHAHAHAHAHAHAHHAHA! I've done fixed it!

Quote:

# Right click on the Application Pool and select “Advanced Settings…”
# Change the “Enable 32-bit Applications” to True)

in IIS. Fuck you Microsoft with your daftness!

Zardoz · **Posted:** Tue Nov 17, 2009 17:37

Nice one Dimmers!

What the hell was Craster droning on about then?

Cras · **Joined:** 30th Mar, 2008 **Posts:** 49244

Tosh!

Dimrill · **Posted:** Tue Nov 17, 2009 17:40

It's the stupid segregation of 32 bit applications from 64 bit applications, and having to manually use the same fucking program under two separate locations to achieve the link to the DSNs. I'd assumed it was my code that was fuckeded, but thinking a bit clearer while typing out the problem made me realise that it really should be IIS's problem. Had a quick fumble in the advanced settings and noticed that the enabling of 32-bit application ODBC access was set to "false" as default FOR FUCK KNOWS WHAT REASON.

markg · **Joined:** 30th Mar, 2008 **Posts:** 16636

I stopped using DSN connections for a lot of asp stuff. Making a DSN-less connection is dead easy and you might find it a bit more flexible.

Pretty good summary here:

http://www.stardeveloper.com/articles/d ... 101&page=1

Dimrill · **Posted:** Tue Nov 17, 2009 17:44

Yeah, I tried a DSN-less JET connection, but even that fell over.

Be Excellent To Each Other

Techy webdev localhost problem

Who is online