October 11, 2011 at 10:53 am
I promise not to vent. We need to install SQL2005 ODBC drivers installed on a Windows Server 2008 R2 box. We have media for both 32 and 64 bit SQl Server. We don't need a database, just the client tools and possibility the Management Studio.
Can I install 32 bit SQl Server on that box?
Is it necessary to bundle the service pack or can we install that separately?
The server already has the 2008 sql front end installed. Should we de-install that first?
We have confirmed the 2008 drivers are too current for a very old application we are using.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
October 11, 2011 at 1:07 pm
Do you only need the MDAC for 2005?
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
October 11, 2011 at 1:10 pm
Yes all we need is the MDAC.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
October 11, 2011 at 1:14 pm
October 11, 2011 at 5:22 pm
On Windows server systems MDAC is part of the operating system and it's service packs.
I believe you may be referring to the SQL server native client, if you already have SQL server 2008 tools installed will they not suffice.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 11, 2011 at 5:27 pm
Nope. The app we are using is ancient. What I really wanted was the native client for SQl2005 64 bit. I installed it. This did not fix the problem. I believe the app is so old it won't work on Windows 2008 R2. I wonder if there is a 32 bit compatibility option for that server.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
October 12, 2011 at 2:11 pm
One last stab at it, are you trying the odbcad32.exe located in the C:\Windows\SysWOW64 directory on your 2008 server?
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
October 12, 2011 at 2:28 pm
No I tried installed a 32 bit version of the SQl Client and 2008 R2 would not cooperate. I had to install the 64 bit version of the client.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
October 12, 2011 at 10:43 pm
which driver are you trying to use?
sql native client? (sqlncli 9.xxxx)
sql native client 10? (sqlncli10 10.xxxx)
Sql server? (sqlsrv32 6.xxxxx)
the 64 bit install for sql native client installs both the 32 and 64 bit drivers, so you're ok there.
Is the dsn a system, user or file dsn? User DSN's and 32 bit legacy applications don't play nice on a 64 bit OS. (the registry key for user dsn's is shared between 32 and 64 bit applications, causing the 32 bit application to see the 64 bit drivers that it can't use.) Use a system or file dsn if you can.
October 13, 2011 at 9:15 am
I installed the 64 bit native client for SQL2005. This did not solve the problem.
I ran the app on Windows 2008 32 bit and it worked. Case closed. The app will not work on the 64 bit server O/S.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply