Suppressing an error message in SQL Server 2008

Hi EE,

Is their anyway I could suppress this specific error message as I am unable to trace back to the device requesting the access and it's isn't part of a job that is executed when in the SQL server.

2018-01-22 01:00:00.28 Logon       Error: 18456, Severity: 14, State: 38.
2018-01-22 01:00:00.28 Logon       Login failed for user 'BDC\SQLMAN'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.16.98.70]
2018-01-22 01:00:00.28 Logon       Error: 18456, Severity: 14, State: 38.
2018-01-22 01:00:00.28 Logon       Login failed for user 'BDC\SQLMAN'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.16.98.70

Any assistance is welcome.

Thank you.
ZackGeneral IT Goto GuyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mark WillsTopic AdvisorCommented:
Unfortunately No.

Cannot suppress the error.

You will need to spend the time to track it down and resolve.

That error does happen for a few different reasons. Basically saying the "user" can no longer login to the database. So, has anything changed at your site ?

Have a read of https://blog.sqlauthority.com/2017/09/19/sql-server-login-failed-error-18456-severity-14-state-38-reason-failed-open-explicitly-specified-database/
0
Scott PletcherSenior DBACommented:
You could try this.  In SSMS, right-click on the instance ("server") name and select "Properties".  On the "Security" tab, change the "Login auditing" value to "None".  Note that this is NOT recommended practice, of course.
0
Mark WillsTopic AdvisorCommented:
Have you read through ErrorLogs ?

Read : http://sql-articles.com/articles/troubleshooting/troubleshooting-login-failed-error-18456/

The first part lets you know how/where to read the errorlogs. There is typically more detail to be found.

Try tracking it down properly first....
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Vitor MontalvãoMSSQL Senior EngineerCommented:
Can't you really verify what machine has the IP 172.16.98.70?
You can also try to check if the default database for user BDC\SQLMAN exists or even if there's any default database configured (if not, configure a default database for that user - one that he has permissions to).
1
ZackGeneral IT Goto GuyAuthor Commented:
Hi Mark/Vitor,

The description of the issue has all the information the error logs provided.

I have tried tracking the ip address it just leads to another SQL cluster not an actual client ip.

I will try running SQL Profiler tonight and see if that provides more information.

Thank you.
0
Mark WillsTopic AdvisorCommented:
Yep, good move. Also check Windows ErrorLog (event viewer) could be the other machine reckons it has a need to connect - linked servers maybe ?  Or looking for services provided by your 2008 machine ?

There will be a reason....
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
I have tried tracking the ip address it just leads to another SQL cluster not an actual client ip.
Well, a SQL Server instance can also be a client for another SQL Server instance. It depends how you're using the databases. I can see some usages that fits on this situation, as Replication, SQL Agent jobs or SSIS Packages, to name few.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ZackGeneral IT Goto GuyAuthor Commented:
Found the culprit finally it was substep in a scheduled job. Thank you for job.
1
ZackGeneral IT Goto GuyAuthor Commented:
Found the culprit finally it was substep in a scheduled job. Thank you for the assistance.
0
Mark WillsTopic AdvisorCommented:
Congratulations, that is good news. Now you can rest easy, Can take time to track down, but always worthwhile.

Again, a big well done to you :)

Regards,
Mark Wills
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.