Can't start MSSQL Service Agent
I rebooted my server following a MS SQL STUDIO Express uninstall and ever since then. MSSQL Service will not start. There is an error mentioned interactive server logon not allowed and it was associated with the sql server I am trying to start. Most of the errors are timeouts. I have tried domain accounts to start the service. I have unchecked the allow service to interact with Desktop and tried to start. It is using the local system account currently. Below are some event log errors that might help.
Faulting application name: sqlservr.exe, version: 2005.90.5000.0, time stamp: 0x4d02a863
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0xc06d007e
Fault offset: 0x0000b9bc
Faulting process id: 0x14c4
Faulting application start time: 0x01cf026a4f34a0c5
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\
Faulting module path: C:\Windows\syswow64\KERNEL
Report Id: 8cef7af3-6e5d-11e3-b045-00
next one
event id 11
source SQLBrowser
The SQLBrowser service encountered a critical failure.
source MSSQLSERVERADHELPER
EVENTID 100
'0' is an invalid number of start up parameters. This service takes two start up parameters.
Faulting application name: sqlservr.exe, version: 2005.90.5000.0, time stamp: 0x4d02a863
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0xc06d007e
Fault offset: 0x0000b9bc
Faulting process id: 0x14c4
Faulting application start time: 0x01cf026a4f34a0c5
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\
Faulting module path: C:\Windows\syswow64\KERNEL
Report Id: 8cef7af3-6e5d-11e3-b045-00
next one
event id 11
source SQLBrowser
The SQLBrowser service encountered a critical failure.
source MSSQLSERVERADHELPER
EVENTID 100
'0' is an invalid number of start up parameters. This service takes two start up parameters.
Suliman Abu Kharroub
Had you tried to install SP3 for sql 2005 ?
ASKER
I haven't.
I am trying to avoid that. the main sys admin is on vacation.
I am trying to avoid that. the main sys admin is on vacation.
ASKER
here are two errors I found in the errorlog
013-12-26 12:28:58.35 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2013-12-26 12:28:59.21 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
013-12-26 12:28:58.35 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2013-12-26 12:28:59.21 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Try setting the MSSQLServerADHelper service to manual. SQL Server will start and stop the service itself when needed. You should let SQL Server manage it.
ASKER
ADHelper will not start either
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes i set it to manual and tried
attached is the error when trying to start it manually
experts-sql-error.JPG
attached is the error when trying to start it manually
experts-sql-error.JPG
Are YOU trying to start it manually because it should not be started manually? Or are you saying that with it being stopped and set to manual you are still getting this error?
ASKER
I don't need it to run as far as I know
the database our application uses will not start....
it is currently set to manual and when I try to start it.
that's the error I get
I don't think I need it
the database our application uses will not start....
it is currently set to manual and when I try to start it.
that's the error I get
I don't think I need it
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Unfortunately, SQL Server Express does not support SQL Server Agent.