May 21, 2012 at 11:07 am
All,
I am getting the below error every minute in one of the production server.
Message
Login failed for user 'ashok'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
Error: 18456, Severity: 14, State: 5.
I don't see login 'ashok' neither on SQL Instance nor Windows Server.
Please advice.
May 21, 2012 at 11:26 am
pawana.paul (5/21/2012)
All,I don't see login 'ashok' neither on SQL Instance nor Windows Server.
That would certainly explain why the attempt is failing.
Something somewhere is trying to make a db connection with 'ashok' as the username. Tracking this down on a forum is nearly impossible. It could be anything.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
May 21, 2012 at 11:33 am
Thank you very much. I'll try to investiage and will keep you posted.
May 21, 2012 at 5:51 pm
If it's happening every minute, I'd be willing to bet someone has a SQL Agent job set up to check something on a dev server every minute and they've pointed it to the wrong box. Check your developers and their servers. Somewhere a job scheduled to run every minute has been failing regularly. 🙂
May 21, 2012 at 10:50 pm
David Webb-200187 (5/21/2012)
If it's happening every minute, I'd be willing to bet someone has a SQL Agent job set up to check something on a dev server every minute and they've pointed it to the wrong box. Check your developers and their servers. Somewhere a job scheduled to run every minute has been failing regularly. 🙂
Yes, I agree with David. It could be a recurring job with a lo-gin specified a "Ashok".
May 22, 2012 at 1:28 am
well you dont have a login on the SQL server for the name Ashok.
I would run a profile trace, select the blank template, then select the Audit Login Failed event from the events selection then look where it is actually logging in from.
I had the same on a box where I had migrated but the dev's hadn't updated the services and it was logging the same error with <local machine> but was actually coming from a different server.
May 22, 2012 at 8:20 am
Thank you very much for your help. As per your advice, I turned ON profiler for Audit Login Failed. The application name is Report Server on the same box. I turned OFF the Reporting Services, the alerts stopped. Right now we are not using reporting services, stopping Reporting services will not hurt. Going forward, if we need reporting services, again failed alerts will start coming.
We are not using SQL Server Agent as there are no Jobs scheduled. There is no way that the alert is coming from SQL Agent Job. There are many items scheduled through task scheduler and nothing related to Reporting Services. Please let me know if you or anyone can think of where this application reside on this box.
May 22, 2012 at 8:26 am
if it is SSRS, it could be custom code within a report, the unattended execution account, a data source, a subscription which keeps firing, an app which utilises the reportviewer.aspx control to render reports, there are many different things which could cause SSRS to connect to SQL.
May 22, 2012 at 8:35 am
Got it. Thank you very much for your help.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply