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.

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.sql

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.

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.

login and sql data base

I make my login account data base using the Web Site Administration Tool in the solution explorer i then debug it on my computer and it works fine i can login then i upload my site and sql data base to server and it no longer works i just get this message what do i do can i change theWeb Site Administration Tool so that it uses a access data base by default for login instead of sql.

Server Error in '/KRAZYJON' Application.

---

Failedto generate a user instance of SQL Server due to afailure in startingthe process for the user instance. The connection will be closed.

Description:Anunhandled exception occurred during the execution of the current webrequest. Please review the stack trace for more information about theerror and where it originated in the code.

SQLExpress database file auto-creation error:

Theconnection string specifies a local Sql Server Express instance using adatabase location within the applications App_Data directory. Theprovider attempted to automatically create the application servicesdatabase because the provider determined that the database does notexist. The following configuration requirements are necessary tosuccessfully check for existence of the application services databaseand automatically create the application services database:

Ifthe applications App_Data directory does not already exist, the webserver account must have read and write access to the applicationsdirectory. This is necessary because the web server account willautomatically create the App_Data directory if it does not alreadyexist.If the applications App_Data directory already exists, the webserver account only requires read and write access to the applicationsApp_Data directory. This is necessary because the web server accountwill attempt to verify that the Sql Server Express database alreadyexists within the applications App_Data directory. Revoking read accesson the App_Data directory from the web server account will prevent theprovider from correctly determining if the Sql Server Express databasealready exists. This will cause an error when the provider attempts tocreate a duplicate of an already existing database. Write access isrequired because the web server accounts credentials are used whencreating the new database.Sql Server Express must be installed on the machine.The process identity for the web server account must have a localuser profile. See the readme document for details on how to create alocal user profile for both machine and domain accounts.

Source Error:

An unhandled exception was generated during the execution of thecurrent web request. Information regarding the origin and location ofthe exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException (0x80131904): Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.]
 System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735043
 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838
 System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +33
 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628
 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170
 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130
 System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27
 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +47
 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
 System.Data.SqlClient.SqlConnection.Open() +111
 System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +68
[HttpException (0x80004005): Unable to connect to SQL Server database.]
 System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +124
 System.Web.Management.SqlServices.SetupApplicationServices(String server, String user, String password, Boolean trusted, String connectionString, String database, String dbFileName, SqlFeatures features, Boolean install) +86
 System.Web.Management.SqlServices.Install(String database, String dbFileName, String connectionString) +25
 System.Web.DataAccess.SqlConnectionHelper.CreateMdfFile(String fullFileName, String dataDir, String connectionString) +397

This may cuased by the IIS account (5.0 is ASPNET and 6.0 is NT AUTHORITY\NETWORK SERVICE) used to connect to SQL is not allowed to generate the user instance. I'm sorry to say that I don't know how to give the permission to the account, maybe you can try to add the IIS account to local machine Administrators group. You can also remove the User Instance attribute from your connection string if you do not need it. To learn more about the User Instance, take a look at:

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

And here is a link for SqlConnection.ConnecitonString:

http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring(d=ide).aspx