April 27, 2015 at 3:59 pm
Hi,
We are getting login failure message every 10 sec.
We are using Sql standard edition 2008r2. We have two sql servers Sql Server1 & sql server2.
Sql Server 1 has login Test and it is connected to some databases with dbowner and default database is master. Same login is existing in server 2 also.
I am getting the following errors in sql server1
Error: 18456, Severity: 14, State: 38.
Login failed for user 'Test'. Reason: Failed to open the explicitly specified database. [CLIENT: Sql Server2 ]
I mapped the master database to the test login in sql server1 but still getting the same errors.
From the sql profiler trace, I can see the database name is Master
Any help to solve this issue. Error log is filling quickly and not able to see other errors
April 28, 2015 at 3:19 am
If your server was installed as case sensitive, then you should use database master instead of Master.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
April 28, 2015 at 9:10 am
SQL_Latin1_General_CP1_CI_AS is the sql server collation
April 28, 2015 at 9:51 am
You need to investigate what application, on the server listed in the error message, is causing the error. It has nothing to do with the default database for the login, as the error says "Failed to open the explicitly specified database.".
The login attempt is explicitly specifying a database that does not exist, you need to identify where the login is coming from, what database is is explicitly requesting and either fix the login request or locate a copy of the DB for the server.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 28, 2015 at 11:28 am
I know the host name where the login is trying to connect and from the profile I can see the database name is master
April 28, 2015 at 11:35 am
Are the two servers on different domains? I've seen this when servers are built or SQL is installed on the same domain, then one is moved to another domain etc...
As suggested before, you can try to get the information from the error log to see which server is failing to connect. Otherwise, test a linked server connection and query the database that way. If that works, it might be something else wrong.
If possible, try a SQL login rather than Windows NT when connecting to the database.
April 28, 2015 at 4:43 pm
We don't have domain so we are using Sql logins only
April 28, 2015 at 6:12 pm
Like Gail pointed out, the error is saying it can't open the explicitly defined database. The connection is made, but look in the connection string for the initial catalog. You know the host name, so find out who's using it. Then you'll have someone to talk to about it and figure out what they're doing. If they're trying to use something and it doesn't work, they might know what it is.
April 29, 2015 at 8:32 am
Thank you.
That login is using in all applications but I didn't get any complaints from application team.
I will find out the dropped database name.
May 8, 2015 at 10:11 am
From the trace, I find the login is trying to reach a db that is not existing.
Is there any way to find when was the database renamed or dropped?
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply