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 |
|
ajacques
Starting Member
2 Posts |
 Posted - 2004-12-31 : 18:21:12
|
| I have SQL Server 2000 installed on a WinXP Pro machine with a local server named AGJ. When I use Enterprise Manager, I have no problem connecting to any of the databases on the machine. When I try to use the Query Analyser, it asks for a login and nothing seems to work, using Windows Authentication, or SQL's sa account, I get the same message (incidentally, the only server available is local):Unable to connect to server AGJ:[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access deniedWhen I go into the ODBC Administrator and look there, there is a System DSN for LocalServer using a SQL Server driver, but when I click on the configure button and try to login to the database, I get a little more info:Connection failed:SQLState '01000'SQL Server Error: 2[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen(Connect()).Connection failed:SQLState '08001'SQL Server Error: 17[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access deniedI want to do development work on the machine for a web site and will need to use the query analyzer and ADO.net to get to the data. Any help will be greatly appreciated.-Al Jacques |
|
|
steamngn
Constraint Violating Yak Guru
306 Posts |
Posted - 2004-12-31 : 22:22:52
|
| This could be a number of things, but for starters, make sure you have the latest service pack for SQL server(3) and for MDAC. Services must be running, as you can connect using EM. Have you tried logging in using sa?AndyThere's never enough time to type code right, but always enough time for a hotfix... |
 |
|
|
ajacques
Starting Member
2 Posts |
Posted - 2005-01-01 : 00:31:58
|
| Thank you for replying on New Year's Eve - and I hope you have a Happy New Year.I will check the service pack and upgrade if necessary. I have been trying to log in as sa and even reset the password in the EM just to make sure I had it right, but that is when I get the error messages. I'll add another reply after the upgrade.-Al Jacques |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-01-01 : 14:17:16
|
| Make sure you have a network protocol enabled also. Go to the Server Network Utility and make sure TCP/IP is enabled.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
steamngn
Constraint Violating Yak Guru
306 Posts |
Posted - 2005-01-01 : 19:54:38
|
| Yup,Sounds like there is no protocol... EM will connect without it, but nothing else will...Happy New Year!There's never enough time to type code right, but always enough time for a hotfix... |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2005-01-03 : 14:02:50
|
| I think this is still the case... Windows XP Service pack 2 is supposed to lock down the TCP/IP and by doing so the connection to SQL Server will have problems. So if it was working before and it stopped working after XP service pack 2, you might want to try connecting with named pipes, but it sounds like they got you fixed up.DanielSQL Server DBA |
|
|
|
|
|
|
|
|
Fail to connect except in Enterprise Manager