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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-05-01 : 08:54:04
|
| Joe writes "Myself and a co-worker today were unable to connect to our 2 SQL 2000 servers. 3 of our other co-works could use Enterprise Manager to connect to both servers. I'm running W2K, sp2. I infrequently use SQL EM so I don't know how long the problem has been manifested. I have removed SQL Client and Tools and reinstalled with SP2. I can register the server, the green start arrow appears in EM next to the servers, it's just when I try to connect I recieve the error in the subject line of this message. Prior to SP2, I was getting "invalid attribute/option identifier" Nothing I've tried works, my Technet subscription has nothing to offer... short of wiping out our machines and reloading everything, I have no idea where to go with this from here.Any suggestions greatly appreciated!Regards,Joe" |
|
|
Kevin Snow
Posting Yak Master
149 Posts |
Posted - 2002-05-01 : 15:59:40
|
| Verify the version of your SQL SERVER ODBC driver compared to that of the machines that are working.The reinstall of the SQL 2000 client should have fixed it. Did you fully uninstall the client tools before reinstalling? |
 |
|
|
Kevin Snow
Posting Yak Master
149 Posts |
Posted - 2002-05-01 : 16:06:16
|
| Found this:Error MessageMicrosoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Driver Manager] Data source name not ?? CauseThis appears to be an issue with the order in which software is installed and uninstalled on the computer. If the ODBC core files become unsynchronized (they should all be the same version) you may see this error. Install the latest version of MDAC (Microsoft Data Access Components) from the following Web site to update all the core ODBC drivers: http://www.microsoft.com/data/ |
|
|
|
monkeybite
Posting Yak Master
152 Posts |
Posted - 2002-05-01 : 17:23:01
|
| Are you able to connect using Query analyzer?If not, you may want to add or check the entry for your SQL server in the Client Network Utility to make sure it's using the right protocol, i.e. TCP/IP or Named Pipes.Also, in the past I've had to make entries in my hosts and lmhosts files to map the NETBios Names of my SQL boxes to IP addresses. You'll find these files in C:\WINNT\System32\Drivers\etc\ (or the drive letter that your OS is installed on). For some reason, my SQL EM had timed out before resolving the name of the server, and I was getting the same errors you described. Several of my clients have had to do this to access SQL Server through firewalls.-- monkey |
|
|
|
|
|
|
|
|
Data Source Name Not Found & no default driver specified