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 |
|
MRTrevorF
Starting Member
1 Post |
 Posted - 2005-08-11 : 14:17:35
|
| I've been working with SQL Server 2000 for the past 2 years now. We're replacing the old server with a new one, and I'm in the process of migrating the databases over one by one. I moved the first one over and created the necessary user profile (SQL Authentication).Problem, though: I get the above error message when I try to connect to the database from my workstation. How do I know the connection string is correct, and that the name is spelled correctly and the server is running? Easy. If I log off my test machine and log back on as Administrator, the same connection string that previously failed now works flawlessly.I don't know why this would be - the logon is based on SQL authentication, NOT windows. SQL Server is configured for Mixed access.Right now, Administrator is the only profile on the new server. My regular profile (the one that produces an error) has full Admin rights, but is still denied - so I think the Server is only admitting requests from another 'Administrator' named accounts.The only differences between the old and new servers, to my knowledge, is that we installed SP1 for Microsoft Server 2003 on the new one.If the problem is in a security setting with SP1 - does anyone know what I need to change, or can point me in the right direction?Any help would be appreciated.Trevor FairchildProgrammer / Analyst |
|
|
Thrasymachus
Constraint Violating Yak Guru
483 Posts |
Posted - 2005-08-11 : 15:45:05
|
| is it possible you moved database users over without the sql server logins which I believe are in master. What was it sysusers or sysxlogins? Both? Don't remember. Check it out.====================================================Regards,Sean RoussyThank you, drive through |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-08-11 : 15:57:38
|
| I've never seen this error actually mean Access is denied. Each time I have seen this error it means that the server is down, the MSSQLSERVER service is stopped, network problems between the client and the database server, or incorrect port being used from the client. Since it sounds like the first two aren't the case, I'd suggest adding an alias on the client using Client Network Utility. Make sure to specify the port that was used during SQL Server installation or via Server Network Utility. If you don't know the port number, simply go to Server Network Utility from the database server, select TCP/IP, then properties. Let us know if you need help with the alias.Tara |
|
|
|
|
|
|
|
|
SQL Server does not exist or access denied.