Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an application that I am migrating from SQL 2000 to 2008. This has gone mostly smoothly. The local machines running Win XP and the VB6 application are working. One machine (only one I can get to directly) runs Win Server 2003 and it works OK. However, the workstations at the remote location are running the VB6 app on Windows 2000. Those do not work.

My question is: what might be missing or out-of-date on the Win 2000 machines, if anything, that would prevent them from working with SQL Server 2008.

share|improve this question
Can you give a little more information about any errors? What are you using to connect to the server? If you're using the SQL 2008 Native Client in your app, it requires XP SP2 or newer. System Requirements for SQL Server 2008 Native Client Can you post your connection string? – squillman Jan 18 '10 at 22:49
Definately not using SQL 2008 Native Client. Using MDAC that was installed with app 10 years ago. Do not have access to machines. However, do know that machines at local installation are Win XP also using MDAC KB870669. Connection string is: Driver=SQL Server;Server=z;Database=yy;App=XXXX;UID=me;PWD=sa; With names changed to protect the innocent. – Jim R Jan 18 '10 at 23:14
Also, VB program is using ADO and MDAC – Jim R Jan 18 '10 at 23:16
Ok, then definitely start with updating MDAC like techie007 suggested. – squillman Jan 18 '10 at 23:18
up vote 5 down vote accepted

Without knowing which error message(s) you're getting, or what methods you are using to connect to the SQL server I'd say your first bet is to ensure the Win 2000 machine(s) have updated Microsoft Data Access Components (MDAC) installed. You can get MDAC 2.8 SP1 from MS here.

share|improve this answer
I will get remote tech to check MDAC and update in the morning. – Jim R Jan 18 '10 at 23:16
Thanks, I did have the remote tech update MDAC as you suggest (also thanks to squillman). But the problem turned out to be that all of the workstations at the remote location had an entry in the hosts file explicitly pointing to the IP address of the legacy server and, of course I shut that down when I started the upgraded server and put in a DNS entry to redirect the old server name to the new one. Of course the hosts file entries made all that moot. – Jim R Jan 19 '10 at 18:23
Good ol' HOSTS. ;) Glad to hear you got it figured out. – techie007 Jan 19 '10 at 20:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.