Cannot open database "xx" requested by the login. The login failed.

Cannot open database "xx" requested by the login. The login failed.

• Naolin

  Can you check your server errorlog and post the errors that show up there Also, does this happen during server startup by any chance Is your database on a special volume, such that it would take longer to start up, for example, is it on an EFS volume

  Thanks
  Laurentiu
  

  
  
  

• LouArnold

  Hi Laurentiu,

  sorry for the delay in getting back to you.
  
  There are no error entries in the primary sql server error logs
  Only an error pops up in the secondary (mirror) server, stating the login failed.
  And this of cours makes sense, as the connection does not go to the primary but to the secondary, which is acting as mirror. And therefore can not be accessed.
  
  The question is : why does the connection sometimes jumps in stead from the primary server, to the mirror server Nowhere in my code I give a secondary server as reference.
  
  The connection is made through ODBC in an ASP web application (IIS6) , simelar to :
  
          Set oCn = Server.CreateObject("ADODB.Connection")
          oCn.CommandTimeout = 180
          oCn.Open lconstirng lconstring
  
         where lconstring is a dsn param : e.g. "filedsn=c:\data\dsn\mastercon.dsn"
         where the dsn file contains following info :
  
  

  [ODBC]
  DRIVER={SQL Native Client}
  UID=myuserid
  pwd=mypwd
  Address=xxx.yyy.zzz.qqq,myport
  Network=DBMSSOCN
  DATABASE=MyDatabaseName
  WSID=xxx.yyy.zzz.qqq
  APP=Microsoft Open Database Connectivity
  SERVER=xxx.yyy.zzz.qqq
  Description=blabla
  

  
  I tried the above without the DSN, so a dsnless connection string. Nothing changed.
  I tried following drivers :{SQL Native Client} and SQLNCLI
  Nothing changed
  
  Any ideas
  
  
  
  Greets
  Tom
  
  

• jbujold

  I have this problem when I bootup system, a startup application try to connect to SQL Server 2005 Express database through ODBC. The return message is like "Cannot open database "GDxData" requested by the Login. The login failed.".

  The SQL Server Log shows a couple entries,

  Login failed for user 'sa'.[CLIENT:....]

  Error: 18456 Severity: 14 State: 16

  This failure only happens I run the application as a startup. In other words, the application does not have problem to connect to database later.

  The database files are located on the SQL Server default data folder.

  'sa' is the database owner.

  Please help.

  Thank you.

  Henry

  
  

• Antonio Romano

  Looks like your application attempts to login using "OBJECTS" as the default database and the database does not exist. Is that database supposed to always exist or is it occasionally dropped and recreated Your application should not attempt to connect to the database if it might not exist.

  Thanks
  Laurentiu

  
  
  

• herocomplex

  If you hit the error again, can you please provide the errorlog entries

  Thanks
  Laurentiu

  
  
  

• A Bodnar

  You are probably attempting to connect before the database is being started. The application should retry connecting after a delay.

  Thanks

  Laurentiu

  
  
  

• iterationx

  Hi Laurentiu,
  
  I'll check the correct SQL serverlogs when this error occurs.
  
  The server is not starting up but running as normally. Remember, this is a production server.
  No special volumes.
  
  Additional information :
  
  As told the connection is made in our ASP pages , using an ADO connectionstring.
  
  Now it seems that the initial connection setup works :
  e.g
  
  set pCn = Server.CreateObject("ADODB.Connection")
  pCn.connectionstring=lstr
  pCn.Open
  
  And the first executes always seem to work :
  e.g.
  pcn.Execute ("select * from thetable")
  
  But in the same page, more executes are performed with the same connection (pC).
  And after some executes, it fails with the above error.
  
  Again, this does not happen always, and not with the same database !
  And we are not starting up the server, or doing special tasks (aka backups,etc) which would add an extra load on the server.
  The moments that this error occures are random, as are the databases with which the error occurs.
  
  Greetings
  Tom
  
  
  

• dnetmgr

  Hi Laurentiu,
  
  
  the database always exists. So it must always be available for connection.
  But for some reason SQL fails to see the database.
  
  Also, it's not one and the same database that has this problems. We have more than 100 databases on the sql server, and the connection error popups randomly with other databases.
  
  Greets
  Tom
  
  

• Vojislav01

  Hi Tom,

  For these questions, I suggest trying the Database Mirroring forum or the SQL Server Data Access forum. These are the forums that address issues related to mirroring and server connections.

  Thanks
  Laurentiu
  

  
  
  
• Cannot open database "xx" requested by the login. The login failed.