January 10, 2018 at 4:45 am
Dear Everyone
Happy new year and i hope everyone is doing great
On one of our production databases version :
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
I keep getting the error below every minute even after disabling all jobs in the SQL Server Agent job list
Date 1/10/2018 12:52:11 PM
Log SQL Server (Current - 1/10/2018 12:35:00 PM)
Source Logon
Message
Login failed for user 'DOMAIN\userx'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
I checked the mappings and this user is mapped to master and msdb but nothing else
What could be causing it to generate this error every minute?
have a good day
Hurricane
January 10, 2018 at 1:26 pm
Does the login have connect on it's default database or the database specified in the connection string it's using?
January 10, 2018 at 1:45 pm
hurricaneDBA - Wednesday, January 10, 2018 4:45 AMDear Everyone
Happy new year and i hope everyone is doing great
On one of our production databases version :
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)I keep getting the error below every minute even after disabling all jobs in the SQL Server Agent job list
Date 1/10/2018 12:52:11 PM
Log SQL Server (Current - 1/10/2018 12:35:00 PM)Source Logon
Message
Login failed for user 'DOMAIN\userx'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]I checked the mappings and this user is mapped to master and msdb but nothing else
What could be causing it to generate this error every minute?
have a good day
Hurricane
Do you have any monitoring setup?
If it's coming from the server itself, look for anything setup on that server which would be logging in. You'd also want to consider any third party agents installed on that server that access SQL Server.
Sue
January 10, 2018 at 1:50 pm
Sue_H - Wednesday, January 10, 2018 1:45 PMhurricaneDBA - Wednesday, January 10, 2018 4:45 AMDear Everyone
Happy new year and i hope everyone is doing great
On one of our production databases version :
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)I keep getting the error below every minute even after disabling all jobs in the SQL Server Agent job list
Date 1/10/2018 12:52:11 PM
Log SQL Server (Current - 1/10/2018 12:35:00 PM)Source Logon
Message
Login failed for user 'DOMAIN\userx'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]I checked the mappings and this user is mapped to master and msdb but nothing else
What could be causing it to generate this error every minute?
have a good day
HurricaneDo you have any monitoring setup?
If it's coming from the server itself, look for anything setup on that server which would be logging in. You'd also want to consider any third party agents installed on that server that access SQL Server.Sue
What other databases do you have on this server and are they accessible? In a mirrored database scenario, an application can be configured to use a connections string where a failover is defined. It is possible that the application is doing connectivity test against principal and mirror. In that case, you will see this type of message on the mirror server.
January 10, 2018 at 6:57 pm
Does someone have a Windows job scheduled? Do you have a system "monitor" piece of software somewhere that's trying to login? Also, you need to figure out who "userx" is. Someone may be trying to tap your machine in a slow manner so as to not raise suspicions or someone's desktop box has some piece of software that regularly hits your database. It might be something like RedGate Source control or, like I said earlier, some piece of monitoring software. If you look at the SQL Server log, you might be able to get more info to try to trace it to the machine.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2018 at 3:39 am
Thanks everyone for the help
It turns out that i moved the Reporting Services Database to another server and the services was still running so it was calling for the domain user i had initiallly initializes RS with.
Upon disabling the windows service the error stopped generating
thank you
Have a great week
Kal
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply