August 23, 2004 at 11:45 am
Hello,
Everytime the sql service starts, login failed are logged in the errorlog, (I have enabled the Audit Level to log the failed logins). These events happens before the service logs "starting up database xxxx". The accounts that are logged corresponds to applications, services and scheduled tasks running with the affected accounts.
I'm about to deploy the "Account Lockout Policy" in the domain and I wonder if this could be something that could give me troubles, since I use these accounts in many things.
I've searched the MS Knowledge Base and google and nothing comes up.
I think this happens because the service is starting and at that time hasn't finished to start up all the databases and my accounts try to connect to a database that hasn't started yet. (It's just my opinion)
Does someone know if there is something I can do?
Regards,
Jose Oyervides.
August 23, 2004 at 2:15 pm
Right click on the icon My Computer. Select Manage. Go to Services. In services find each service for the applications that need to connect to SQL Server. One solution is to make them all dependent on MSSQLServer service or the SQLServerAgent service. Once you make them dependent on another service they can't start until that service is up and running. That's why you can't start SQLServerAgent service unless the MSSQLServer service is running. (the agent service is dependent on the server service).
The problem with this is that you won't be able to run those applications unless SQL Server is running.
-SQLBill
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply