February 23, 2012 at 9:57 am
could not start the SQLSERVERAGENT service on local computer Error 1068: The dependency service or group failed to start
This is the error I get, NetLogon Service is working, and both the jobs are using the Local System Account,
Help is Highly Appreciated,
Thanks,
Dave
February 23, 2012 at 10:03 am
Is the database engine running?
Jared
CE - Microsoft
February 23, 2012 at 10:19 am
check the event viewer for more information
February 23, 2012 at 10:28 am
yes database engine is running, but th issue with the services
February 23, 2012 at 10:33 am
A 1068 error means one or more of the required services is not running... So... Which services are stopped?
Jared
CE - Microsoft
February 23, 2012 at 10:35 am
MSSQLSERVER and SQLSERVERAGENT
February 23, 2012 at 10:40 am
dsohal (2/23/2012)
MSSQLSERVER and SQLSERVERAGENT
If MSSQLSERVER is stopped, then the database engine is not running. MSSQLSERVER must be running in order to start SQLSERVERAGENT service.
Jared
CE - Microsoft
February 23, 2012 at 10:42 am
Yes please MSSQLSerice is not starting
February 23, 2012 at 10:48 am
Ok, now you have to go to the event viewer and see why it is not starting. Or, go to SQL Server Configuration Manager and try to start it from there. It should give you a more detailed error that you can post here.
Jared
CE - Microsoft
February 23, 2012 at 10:54 am
this is a message I get in the event properties,
18052 :
Error: 9003, Severity: 20, State: 1
February 23, 2012 at 11:02 am
Did you recently delete any folders? ...\MSSQL\DATA or ...\MSSQL\LOG
These folders need to be in the configured place. You should see an error that says Cannot open specified folder C:\Program Files\...\MSSQL... or something along those lines. Find what path is missing and then create it.
Jared
CE - Microsoft
February 23, 2012 at 11:08 am
No nothing was changed and I see the files there,
February 23, 2012 at 11:25 am
Look in the security and system logs. There should be more information about the starting of the service and the failure.
February 23, 2012 at 11:30 am
Go to your default SQL Server Log folder (...\MSSQL\log\) and look at the error log file.
Jared
CE - Microsoft
February 23, 2012 at 11:33 am
I will check that, Thanks a Lot
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply