SqlException:Login failed for user ABC

Question

0.00/5 (No votes)

See more:

SQL-Server-2005

C#

SQL-Server

, +

Hi,
I get the following exception stack randomly :

Login failed for user ABC.

MSIL

System.Data.SqlClient.SqlException: Cannot open database  MYDatabase requested by the login. The login failed.
Login failed for user  ABC.
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at ConnectionFactory.OpenSqlConnection(SqlConnection connection)

I do not often get this exception but it is mostly at the first logon.
For the next logon everything works fine.

Does it have anything to do with loading/unloading of userprofiles or impersonation?

Any specific reason for this? How can I avoid this?

Posted 18-May-11 2:22am

priy@

Add a Solution

Comments

Dave Kreskowiak 18-May-11 9:58am

WHat kind of app is this? Windows Forms or ASP.NET? What does the connection string look like?

priy@ 26-May-11 8:04am

connection string is "Integrated Security=SSPI;Initial Catalog=MYDatabase;Server=.\\SQLEXPRESS"

priy@ 26-May-11 8:05am

It is an ASP.net app

Dave Kreskowiak 26-May-11 9:34am

If you've got any InnerException message, you'll need it. Right now, there isn't enough information to troubleshoot the problem.

I suggest going through http://blogs.msdn.com/b/sql_protocols/archive/2007/05/16/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error-xxx.aspx.

Dave Kreskowiak 26-May-11 9:35am

If you've got Named Pipes enabled, try disabling it in the SQL Server and Client and stick with straight TCP/IP.

priy@ 1-Jun-11 5:56am

No I do not have any named pipes enabled.
Thanks for the info...although it didnt help.

priy@ 1-Jun-11 6:02am

hOwever while simulating this problem i came across a strange behavior.
I have a small test application which opens SQL connection, waits for 8 ms and then closes that connection.
I am doing this in a while loop.
when thisi test app is running, I goto the task manager (under Processes tab) and kill sqlservr.exe.

I thought that now the test app should throw an exception, but it does not. it still opens and closes the sql connection.
How is that possible when the service itself is not running?

Dave Kreskowiak 1-Jun-11 7:49am

Because you're not really opening a connection to the SQL Server. You're opening the ADO.NET connection (which is automatically pooled). The connection to the SQL Server (from ADO.NET) won't really open until you do something with it.

priy@ 1-Jun-11 8:49am

Thanks Dave...will look into it further

priy@ 1-Jun-11 6:03am

I am passing the same connection string i.e. "Integrated Security=SSPI;Initial Catalog=MYDatabase;Server=.\\SQLEXPRESS"

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)