SQL ODBC Connectivity Problem

Hi Guys, i have a windows 2000 server (lets name it X) with SQL 2000 ODBC driver which am experiencing problem accessing SQL server database on another server (lets take it as Y). The test connection is successfull when i try it from my desktop to Y server but when i try it from that X to Y server no luck. What i noticed was the the SQL ODBC driver version differences. The SQL ODBC driver version on my PC is 2000.85.1117.00 where the version on X server is Anybody has any idea how to upgrade this driver? By the way, is this some thing to do with MDAC? If i install MDAC 2.8 (Microsoft Data Access Component) will resolve my problem. X= Win 2k SP4 Y= SQL server 2000

Thanks for your input.

more ▼

asked Aug 31, 2010 at 07:50 AM in Default

avatar image

1 1 1 1

(comments are locked)
10|1200 characters needed characters left

2 answers: sort voted first

CAn you try this process described here http://jonathanallen69.blogspot.com/2010/04/testing-database-connection-or-who-hell.html from the machine you are having problems with and let us know the results please? It could be MDAC and to my knowledge there is no reason not to have the most recent on all working computers so its worth doing anyway I guess.

more ▼

answered Aug 31, 2010 at 12:42 PM

avatar image

Fatherjack ♦♦
43.8k 79 101 118

Thanks for your reply. I did try this which worked from my PC (win XP) but on my win 2k server. The result is the same as if I try to add DSN in ODBC and this is what I'm getting: Test connection failed because of an error in initializing provider. [Microsoft][ODBC Driver Manager] Data source name not fount and no default driver specified.

Aug 31, 2010 at 01:15 PM amira1344

What is very difficult to understand is the reason to use ODBC. On the top of the fact that ODBC is slow, it is also evil because it stores credentials in registry in clear text. Also, if you accidentally create a user DSN, it writes info into HKCU hive so it is not accessible to others. System DSN writes to HKLM, but depending on the group policy, the attempt to write might fail. Anyway you look at it, it is just plain difficult to find any justification to use it, specifically when connecting to SQL Server.

Aug 31, 2010 at 01:27 PM Oleg

@Oleg - very true. took the question at face value and simply tried to resolve issue rather than see if its necessary. Thanks for posing question ...

Aug 31, 2010 at 01:36 PM Fatherjack ♦♦

@Fatherjack @amira1344 Actually, it does look like the server X in question has very outdated version of MDAC installed. I believe that all MDAC 2.8 flavours should result in something like 2000.8X.YYYY.ZZ for SQL Server ODBC driver, the higher the X the better. The driver is 32 bit, the name of the binary is SQLSRV32.dll regardless whether OS is 32 or 64 bit. This means that installing MDAC 2.8 should resolve the issue.

Aug 31, 2010 at 01:52 PM Oleg
(comments are locked)
10|1200 characters needed characters left

Thank you both. If fact, I am provideing application people to talk with SQL server throuth their program. I don't know any otherway for this kind of access and appreciate your suggestion. @Fatherjack, upgrading to mdac 2.8 was my initial though but don't the outcome. Hopefuly, will not toast me.

Thanks again

more ▼

answered Aug 31, 2010 at 02:44 PM

avatar image

1 1 1 1

(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.



asked: Aug 31, 2010 at 07:50 AM

Seen: 2899 times

Last Updated: Aug 31, 2010 at 07:50 AM

Copyright 2018 Redgate Software. Privacy Policy