May 9, 2014 at 12:22 pm
Hello,
I'm seeing continuous login failure error messages in error log.
Environment :
SQL 2005
Windows 2003
Login : service account ( it is enabled and it has Sa access , and sql and agent services are running under the same service account ).
No one uses this instance, error log gets filled up frequently because of these continuous messages.
I disabled all the job including replication jobs and i have removed replication also, still i'm seeing the same error messages. Not sure who is connecting the instance , i ran a profiler trace to see the activity.
I dont see any different activity except the following, can anyone please help to get rid this issue
EXECUTE msdb.dbo.sp_sqlagent_log_jobhistory @job_id = 0x25A8936F3CA0FE4E92565625F577E97C, @step_id = 2, @sql_message_id = 0, @sql_severity = 0, @run_status = 2, @run_date = 20140509, @run_time = 140311, @run_duration = 1, @operator_id_emailed = 0, @operator_id_netsent = 0, @operator_id_paged = 0, @retries_attempted = 37451, @session_id = 36, @message = N'The replication agent encountered an error and is set to restart within the job step retry interval. See the previous job step history message or Replication Monitor for more information.'
EXECUTE msdb.dbo.sp_sqlagent_log_jobhistory @job_id = 0x25A8936F3CA0FE4E92565625F577E97C, @step_id = 2, @sql_message_id = 0, @sql_severity = 0, @run_status = 4, @run_date = 20140413, @run_time = 105524, @run_duration = 6270748, @operator_id_emailed = 0, @operator_id_netsent = 0, @operator_id_paged = 0, @retries_attempted = 0, @session_id = 36, @message = N'
2014-05-09 18:03:11.941 Copyright (c) 2005 Microsoft Corporation
2014-05-09 18:03:11.941 Microsoft SQL Server Replication Agent: logread
2014-05-09 18:03:11.941
2014-05-09 18:03:11.941 The timestamps prepended to the output lines are expressed in terms of UTC time.
2014-05-09 18:03:11.941 User-specified agent parameter values:
-Publisher xxxxx
-PublisherDB xxxxx
-Distributor xxxxx
-DistributorSecurityMode 1
-Continuous
-XJOBID 0x25A8936F3CA0FE4E92565625F577E97C
-XJOBNAME xxxxx-xxxx-xx
-XSTEPID 2
-XSUBSYSTEM LogReader
-XSERVER xxxxx
-XCMDLINE 0
-XCancelEventHandle 0000000000000920
-XParentProcessHandle 0000000000000EEC
2014-05-09 18:03:12.019 Status: 0, code: 20015, text: ''Cannot open database "xxxxx" requested by the login. The login failed.Login failed for user ''domain\xxxxx''.''.
2014-05-09 18:03:12.019 Cannot open database "xxxxx" requested by the login. The login failed.Login failed for user ''domain\xxxxx''.
May 12, 2014 at 5:33 am
is this ''domain\xxxxx'' is your service account?
if it is are your sure it is Sysadmin in that server, looks like it doesn't have access to the DB as per the error.
Regards
Durai Nagarajan
May 12, 2014 at 6:08 am
Does database 'xxxxx' definitely exist?
May 12, 2014 at 6:29 am
This type of error usually occurs when the default database defined for the login is not accessible by this login (either no permission or does not exist)
May 12, 2014 at 7:30 am
Beatrix Kiddo (5/12/2014)
Does database 'xxxxx' definitely exist?
Thanks for the response...
The database xxxx doesnt exist....i'm not sure where this connection is coming from....
May 12, 2014 at 7:31 am
durai nagarajan (5/12/2014)
is this ''domain\xxxxx'' is your service account?if it is are your sure it is Sysadmin in that server, looks like it doesn't have access to the DB as per the error.
Thanks for the response...
yes, its a service account and it has Sa access on the box and instance.
May 12, 2014 at 8:27 am
Robin35 (5/12/2014)
Beatrix Kiddo (5/12/2014)
Does database 'xxxxx' definitely exist?Thanks for the response...
The database xxxx doesnt exist....i'm not sure where this connection is coming from....
Is there anything in the SQL Server log? It usually gives you the IP address the login is trying to connect from, and you can do a ping -a to get the hostname.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply