March 23, 2018 at 1:57 pm
Hi,
I can see Login Failures as below in SQL Error Logs in our production servers, but the database is not exist on the server, Can somebody help me why login is trying to connect the database which doesn't exist and how do we stop logging this error,
Login failed for user 'XXXXXXXXXXXXXXXX'. Reason: Failed to open the explicitly specified database 'XXXXXXX'. [CLIENT: X.X.X.X]
Thanks
Sunny
March 23, 2018 at 2:42 pm
if the explicitly specified database XXXXXXX is not on the server, you need to figure out what program on client computer X.X.X.X is trying to login to the database and fix its connection string in its configuration. Are the errors all coming from the same client or are they various clients?
March 23, 2018 at 2:45 pm
You can stop getting it by figuring out what app on the client specified is trying to connect to a DB that doesn't exist, because the root cause of this is someone (or some app) explicitly specifying that database as what they want to query.
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 2, 2018 at 2:15 pm
Chris Harshman - Friday, March 23, 2018 2:42 PMif the explicitly specified database XXXXXXX is not on the server, you need to figure out what program on client computer X.X.X.X is trying to login to the database and fix its connection string in its configuration. Are the errors all coming from the same client or are they various clients?
Thanks for your reply, the issue is fixed by rebooting application dependent services in web server.
-Sunny
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply