Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jhunt
Starting Member
21 Posts |
Posted - 2002-01-30 : 10:47:13
|
| Hi thereWe have upgraded our application to run with SQL server 2000 and included MDAC_typ.exe with the distribution. However a small number of our users after installing mdac2.6 can no longer connect to the DB's. My question is how do I repair a users environment that has been damaged by a failed MDAC installation? The situation almost always arises on a low spec or win95/98 machine. Sometimes it seems the user has not stopped the SQL server during the upgrade.MDAC Rollback seems a pretty hairy solution, and can cause even more damage. Help!Justin |
|
|
andre
Constraint Violating Yak Guru
259 Posts |
Posted - 2002-01-30 : 10:51:49
|
| What is the error message they are getting when they try to connect to the database? |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-01-30 : 13:24:51
|
| Download the Component Checker from www.microsoft.com/dataThis tool will tell you the version of MDAC installed, and if there are any mismatched components. It also has some tools for removing and reinstalling on 95/98 machines. Look at the help file for those.-Chad |
 |
|
|
jhunt
Starting Member
21 Posts |
Posted - 2002-01-30 : 17:22:39
|
| The error is something like"[DBNETLIB] Database does not exist or access denied". Though the server is running.Will have another look at the component checker, I was not really able to figure out how I should use it. If it has 95/98 repair stuff it could b useful.ThanksJustin |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-01-30 : 17:27:36
|
| Are you sure the client is trying to connect with the same net lib that the server is listening on?If the server is using TCP/IP, make sure the client network utility on the client has TCP/IP as the preferred method of connecting.-Chad |
 |
|
|
jhunt
Starting Member
21 Posts |
Posted - 2002-02-01 : 05:40:25
|
| Thanks for your help. I think that NETLIB error may be a bit of a red herring because they are connecting to the server locally.Had to go and visit the user, who was pretty upset, and just fixed another machine up for them that would do the job. The existing machine will eventually get rebuilt.I think that it is probably possible to use the component checker as you suggested Chadmat, just did not have the luxury of the time to play around with it and the users environment.Other people just beware of upgrading to MDAC2.6 on Win 95 machines unless they have:Ample Disk spaceDCOM installedClosed all applications using Data Access Components. |
 |
|
|
|
|
|