Login failed for user <user_name>. (Microsoft SQL Server, Error: 18456)

Please help I keep getting this message when I log on to my data base. Not sure what state 1 relates too

TITLE: Connect to Server

Cannot connect to <server_name>

ADDITIONAL INFORMATION:

Login failed for user <user_name>. (Microsoft SQL Server, Error: 18456)

BUTTONS:

OK

Server Name: <server~name>Error Number: 18456
Severity: 14
State: 1
Line Number: 65536

Dear testman,

Check if your sql service is running.

Also check you username/password.

http://msdn2.microsoft.com/en-us/library/ms366351.aspx

HTH,

Suprotim Agarwal

|||

Thanks for your reply.

I have tried: checking passwords and logins, deleting database from te server and re-installing (via helm editor) assigning new admins, switching off interrnet protection, calling sysadmin to check the state of the database server, rebooting my machine.

run out of ideas now

|||

Try to connect to the sql server by giving the port number in which sql listens.....

<ServerName>,<PortNumber> in the Sql server management studio (SSMS)

|||Yes tried this also |||

YOu will have to examine the SQL Server log (and turn on the auditing functionality) to find out what happens behind the scenes. As you already noticed is State 1 a general error state. The definite state can be found on the server logs. So make sure you turned on auditing on the server and login again. Afterwards send the error entry to the forums.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||If you use Windows Vista and SQL Server codename: Katmai, you must to run the Management Studio as administrator!
|||Haven't been able to get hold of the log yet as is remote webhost|||

Okay, this message means you are getting through to the server, but it does not recognize the login credentials your code is supplying. It would help to see the entire ConnectionString (with the actual UserName and Password stripped out). This will tell us a lot about how you're trying to connect.

I would also consult my whitepaper on connecting on my blog (www.betav.com/blog/billva)

|||That worked for me - I had the same problem! Right click the shortcut and select "Run as administrator".
|||Thanks for your help everyone. It was a web server administration problem it all worked when they allowed my connection.