October 17, 2008 at 12:12 pm
Hi,
We are using sql server 2005 on which Sharepoint application runs. I just looking into the error log to make sure everything is fine I found this, error continuosly occuring.
Login failed for user 'Domain\sqlservice'. [CLIENT: IP]
2008-10-16 23:55:05.02 Logon Error: 18456, Severity: 14, State: 16.
Here sqlservice is the service account,used to start all sql services
What will be the solution for this?
and also getting the error:
Error: 17187, Severity: 16, State: 1
SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: IP]
What steps I can take to get rid of these errors?
thanks
October 17, 2008 at 2:29 pm
has the password expired on the service account?
Craig Outcalt
October 17, 2008 at 2:39 pm
October 17, 2008 at 2:56 pm
Thank You..
we had already installed SP2 which includes the hotfix
October 17, 2008 at 3:16 pm
hi,
The password for this service account never expires.
and it says the login failed for the user abc\sqlservice, but in the management studio,security,logins I observerd that abc\sqlservice login does not exist?
Could you plz clarify me...
October 18, 2008 at 11:00 pm
You need to track down what's trying to connect with that account. You could run a Profiler or server side trace with auditing login failures. Make sure you've got the HostName and ApplicatioName columns turned on. That should tell you the information you need to know.
K. Brian Kelley
@kbriankelley
October 20, 2008 at 6:49 am
This is making some sense now.
Is this the SQL Agent trying to start a job and having the login fail?
Craig Outcalt
October 20, 2008 at 11:43 am
I believe an 18456 with state 16 = No permissions for target database or target database offline.
June 2, 2010 at 7:17 am
Tom Schuettke (10/20/2008)
I believe an 18456 with state 16 = No permissions for target database or target database offline.
Having done a fair bit of trawling for reasons for Error 18456 over the last couple of days, it seems that State: 16 can be attributed to various things, including:
* User default database cannot be determined from login properties
* User default database doesn't exist
* User doesn't have permission for the target database
* database is offline
* database is in single user mode.
Just a few things to look at!
Thomas Rushton
blog: https://thelonedba.wordpress.com
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply