Web Development with Visual FoxPro
Re: e: 32 bit ODBC drivers on 64 bit web server unstable work
Messages
Reply
Edit
Delete
Dec. 3, 2012
01:56 pm
3NQ0TVMBD![Show this entire thread in new window]()
01:56 pm
3NQ0TVMBD
| From: | Rick Strahl |
| To: | Helen Novik |
There should be no problem running an ODBC driver from an app IF the server is in fact running 32 bit.
However, you're running IIS5 which doesn't have AppPools and so you can't isolate 'applications' into their own 32 bit worlds - it only has IIS level isolation and so unless you forced the entire server into 32 bit mode, it will still potentially run in 64 bit mode.
I think what probably happens is that your server has both 32 and 64 bit apps and sometimes starts in 64 bit mode at which point the ODBC driver doesn't work until your restart and hopefully hit it with 32 bit first.
I can't recall the details on how 32 bit settings work on IIS5 - I think it was with registry keys?
+++ Rick ---
We recently changed old Windows 2000 web server (IIS 5.0) to a 64 Bit Windows 2008 R2 server (IIS 7.0). Three of our websites use Visual Foxpro 7 databases (classic ASP). I enabled 32-bit applications in the web server application pools, found ODBC Data Source Administrator for the 32-bit ODBC drivers (odbcad32.exe), and set up Use and System DSNs exactly the way they were in the old Windows 2000 server. All three websites work similar, and DSNs look similar (the only difference - they point to a different databases)
Now one of these websites works perfect, other two - unstable. They suddenly refuse to connect. No errors, no log records, just shows status bar "connecting" forever. After several resettings of DSNs and restarting of web sites they work again for some time, than don't work again.
Any suggestions will be greatly appreciated.
Rick Strahl
West Wind Technologies
Making waves on the Web
West Wind Technologies
from Maui, Hawaii
Making waves on the Web
