SQLSERVERAGENT service on Local Computer started and then stopped

  • lllim

    SSC Veteran

    Points: 266

    Hi,
     
    Anyone here could help me on the error "SQLSERVERAGENT service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."
     
    I'm installing MSSQL 2000 on WINDOW 2003.
    When I tried to start the SQLSERVERAGENT service, the error above prompt out.
     
    Any idea?
     
     
    3L
  • Cat Phillips

    SSC Journeyman

    Points: 77

    I also have this problem, sql server 2000 on winxp machine.  Also see Error: 823, Severity: 24, State: 2 in the log.  It is a dual processor machine, and I see on MS knowledge base issues with dual processors in W2K, but it doesn't mention XP.  Is yours dual processor?  I am also running RAID, wonder if that has anything to do with it.  If you are dual processor, try http://support.microsoft.com/default.aspx?scid=kb;EN-US;838765.

    Any help is greatly appreciated.

  • milagros nazar

    SSC Journeyman

    Points: 79

    Give the service account System Administrator privilege on SQL, and try to start the service again.

  • Sugesh Kumar

    One Orange Chip

    Points: 27311

    Can you post the errors that has been reflected in error log of sql server.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • Ivan A Loreto

    SSC Rookie

    Points: 49

    Hi,

    I had the same problem enabling the SQL Srv Agent (2005) on Dual Pentium 4 running XP SP2.

    Make sure these services are enabled and running:

    Event Log : Automatic

    Performance Logs and Alerts : Manual

    Error Reporting Services: Manual

    SQL Server : Automatic

    SQL Browser: Automatic

    SQL Server Agent: Automatic

    Good luck!

     


    GodSpeed,

    Ivan A Loreto

    Applicaiton Analyst II

    Loma Linda University Medical Center

    Transplantation Insitute, CA

  • bill-413410

    SSC Enthusiast

    Points: 107

    I got this error too.

    >>SQLSERVERAGENT service on Local Computer started and then stopped. Some >>services stop automatically if they have no work to do, for example, the >>Performance Logs and Alerts service."

    Here is how I resolved it.

    On our system, MSSQLSERVER and SQLSERVERAGENT both run under a local Windows user called sqluser.

    To resolve, I opened compmgmt.msc->Users And Groups, deleted sqluser completely and re-added him. I then re-added him to be a member of Administrators and Users group.

    I then opened services.msc, RightClicked on Properties for MSSQLSERVER and SQLSERVERAGENT and under the LogOn tab for both, I browsed to the user sqluser and set the password to be the same as that which I had used when recreating the user in the previous step in compmgmt.msc

    The recreation of the user did the trick and I was able to restart both MSSQLSERVER and SQLSERVERAGENT without a problem.

  • cmrhema

    Default port

    Points: 1498

    The above post helped me too

  • EdVassie

    SSC Guru

    Points: 60154

    If you give the SQL Agent service account Windows local administrator rights, you can bypass most security restrictions that might stop Agent from working. However, you are then running Agent with moer rights than it needs.

    In SQL Server 2005, neither the Agent account or the SQL Server account need to have Windows local admin rights.

    1) Look in BOL 'Setting up Windows Service Accounts' and ensure SQL and Agent have the rights specified. Also look at the rights listed in 'Enabling memory support for over 4GB physical memory' and 'Database File initialization'.

    2) Ensure the service accounts have Read authority on the Windows 'Event Log' and 'Remote Procedure Call (RPC)' services. Agent will not run if it cannot determine the status of Event Log.

    3) Ensure the service account used for Agent is defined as a login to SQL Server.

    This should get you past most problems, and avoid the need to run the services with local admin authority.

    Original author: SQL Server FineBuild[/url] 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 14 Mar 2017: now over 40,000 downloads.Disclaimer: All information provided is a personal opinion that may not match reality.Quote: When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist. - Archbishop Hélder Câmara

  • ahmadq

    SSC Journeyman

    Points: 77

    on sql 2000

    i think you have to check if the file xpstar.dll is exist on ur Binn folder or not

    if this file missing you can compy it from any other SQL server and it will fix the problem

    Note i have no idea why this file is missing !!

  • sudhakara

    SSCrazy Eights

    Points: 9425

    its helped me to resolve this issue...

    "The Sql Server Analysis Service (MSSQLSERVER) service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service"

    thnks...

    can you explain the reason behind this issue ?

  • johnphilip

    SSC Enthusiast

    Points: 170

    I had the same problem. To resolve do as follows:

    a) stop all sql services from service manager.

    b) change the logon for the following services from a named user account to local system account and stop the services.

    SQL Server, SQL AGENT, SQL Server Browser,SQL Server VSS writer and SQL Server Reporting(if installed).

    c) After changing, start the services again(in local system account logon)

    d) Once all services start successfully, change the logon account back to the named account which was in use previously. Either restart the machine or stop and start the individual services from service manager.

  • johnphilip

    SSC Enthusiast

    Points: 170

    I had the same problem. To resolve do as follows:

    a) stop all sql services from service manager.

    b) change the logon for the following services from a named user account to local system account and stop the services.

    SQL Server, SQL AGENT, SQL Server Browser,SQL Server VSS writer and SQL Server Reporting(if installed).

    c) After changing, start the services again(in local system account logon)

    d) Once all services start successfully, change the logon account back to the named account which was in use previously. Either restart the machine or stop and start the individual services from service manager.

    This resolved my problem

  • bogdi_p

    SSC Enthusiast

    Points: 101

    It appears that the VIA protocol for MSSQLSERVER is Enabled.

    If you disable it, MSSQLSERVER will start.

    Location for disabling VIA protocol:

    Computer Managment -> Services and Applications

    -> SQL Sever Configuration Manager ->

    SQL Server 2005 Network Configuration ->

    Protocols for MSSQLSERVER -> VIA (if Enabled, disable it.)

    If MSSQLSERVER, still does not start, try starting the service: Distributed Transaction Coordinator from (Run) services.msc. After that disable VIA. 😉 It worked for me.

  • gurvann

    Valued Member

    Points: 55

    Hi everybody,

    I've had this error message with SQLServer Agent service.

    I use a domain account to start this service. This account is not a Local Administrator.

    I've added this account on the specific SQL Agent Group:

    Default instance: SQLServerSQLAgentUser$ComputerName$MSSQLSERVER

    or

    Named instance: SQLServerSQLAgentUser$ComputerName$InstanceName

    The error message i've get was:

    ----------------------------------------------------------------------------

    Services

    The SQLSERVERAGENT service on Local Computer started and then stopped.

    services stop automatically if they have no work to do, for example, the Performance Logs and Alerts Services

    ---------------------------------------------------------------------------------------

    To solve this, i've checked Access control lists for the SQL Agent group.

    To do this, please read the following article:

    http://msdn.microsoft.com/en-us/library/ms143504.aspx

    Now, all is alright 😀

    Good luck !!

    Bye

    Gurvann

  • sudha_sql

    SSC Enthusiast

    Points: 105

    Almost Identical scenario - Solution was to make sure the account being used by SQL Agent Service is a member of the SQL Server SysAdmin group. SQL Server service works fine - even though the account is not a member of teh SysAdmin group.

    Background Info about Environment:

    We recently created a new domain account that would be used to run SQL Server and SQL Agent services for a specific instance in a multi-instance, multi-CPU consolidated server(SQL2005 SP2). I added the domain account to the Local Admins group and opened up services.msc and modified teh logon account information. SQL Server service runs fine - but SQL Agent service would NOT startup.

    Hope this helps somebody(or me the next time I make the same mistake)

    Sudha

Viewing 15 posts - 1 through 15 (of 25 total)

You must be logged in to reply to this topic. Login to reply