February 2, 2006 at 12:56 am
When trying to connect to my SQL Server I'm getting the following error:
******************************************
A connection could not be established to (local).
Reason: Logon failed for user.
Please vertify SQL Server is running and check your SQL Server registration properties (by right-clicking on the (local) node) and try again.
******************************************
SQL Server is definately running, but I'm unable to connect.
I've tried changing the ODBC settings but I can't get past the "MIcrosoft SQL Server DNS Configuration" window. I choose "With Windows NT authentication using the network lognin ID" and click "Conect to SQL Server to obtain default setting for the additional congiruation options" and click "Next" but I get stopped by the following error:
connection failed:
SQLState: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user machine1\Administrator'
Does anyone have any ideas on what I need to do to fix this? If it helps, this all seems to have started occuring since I changed the Administrator password
February 2, 2006 at 4:57 am
Is the sql server running on your pc?
What OS do you have?
February 2, 2006 at 7:54 am
Is your SQL Server set up for Windows Only or mixed authentication?
Is your login set up for Windows only or SQL Server only?
-SQLBill
February 2, 2006 at 12:53 pm
It's setup for Windows Only authentication, and likewise with the login.
February 2, 2006 at 1:03 pm
And you are trying to connect from a remote computer, correct?
Is your computer on the same domain as the SQL Server computer?
-SQLbill
February 2, 2006 at 10:11 pm
Nope, this is actually on the SQL Server computer itself.
February 3, 2006 at 6:40 am
Does Administrator have an account in SQL Server?
Has the SQL Server login BUILTIN/Administrators been deleted or set to deny or anything like that?
-SQLBill
February 3, 2006 at 5:34 pm
>>Does Administrator have an account in SQL Server?
I presume so, I don't know for definiate as I'm unable to login.
>>Has the SQL Server login BUILTIN/Administrators been deleted or set to deny or anything like that?
I presume so, I don't know for definiate as I'm unable to login.
Any further tips Bill?
February 4, 2006 at 3:25 pm
Could you please help Bill?
February 6, 2006 at 8:29 am
Do you have another account to use?
Does anyone else have an account that has sysadmin priviliges in SQL Server?
It really sounds like BUILTIN/Administrator account was deleted. If so, you might be out of luck if no one else has an account that has SQL Server sysadmin priviliges.
Kinda late now, but this is why I have a second account that has sysadmin priviliges, but is strictly an 'emergency' account.
-SQLBill
February 6, 2006 at 8:32 am
One other thing to try...relooking at your first post, you indicate you are trying to set up an ODBC connection. You shouldn't have to do this on the server itself, unless you are using something else (another application) to access the database.
Have you tried logging in by using just Query Analyzer (not via Enterprise Manager)?
-SQLBill
February 6, 2006 at 11:02 am
You never did say what version and edition of SQL Server you are using nor what operating system you are running. I'll assume SQL Server 2000.
Do you know the sa password? If so, change the value of the following registry key to 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\LoginMode
This will switch the server to mixed authentication mode. You must stop and restart SQL Server for this to take effect.
Login in with the sa account in Query Analyzer, or edit your server registration in EM. Add a domain account if required. Switch back to Windows Only mode. Stop and restart SQL Server. If you change the EM registration, change it to the Windows account.
NOTE: If you don't know the sa password, you could try using NGSSQLCrack. It can be downloaded at http://www.ngssoftware.com/sqlcrack.htm
February 7, 2006 at 12:34 pm
This error is a common symptom of any one of a couple dozen causes. An excellent article in the Microsoft Knowledge Base will give you the entire run-down: Potential cases of the "SQL Server does not exist or access denied" error message.
Go to the Microsoft Knowledge Base on the web:
http://support.microsoft.com/default.aspx?scid=fh;en-us;kbhowto
and search for: 328306
February 8, 2006 at 2:25 am
I changed it to mixed mode and managed to guess the "sa" password so I'm in!
Someone had changed the Bulletin/Administrators group to "Deny".
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply