Results 1 to 2 of 2

Thread: SQLServerAgent

  1. #1
    kevin Guest

    SQLServerAgent

    What would cause this message to display or what does this mean??
    "Could not start the SQLServerAgent Service, error 2186, the service is
    not responding to the control function"



  2. #2
    Craig Guest

    SQLServerAgent (reply)

    Looks like you need the following tecnet article:
    PSS ID Number: Q183194
    Article last modified on 04-16-1999

    WINNT:6.5

    winnt


    ================================================== ====================
    -------------------------------------------------------------------------------
    The information in this article applies to:

    - Microsoft SQL Server version 6.5
    -------------------------------------------------------------------------------

    SYMPTOMS
    ========

    SQL Executive does not respond to Windows NT Service Control Manager (SCM). It
    fails, displaying error 2186 as follows:

    Error 2186 The service is not responding to the control function.
    Could not start the SQLExecutive service on \Server.

    CAUSE
    =====

    This problem can occur if there is an ODBC core file version mismatch. The
    distribution task loads the ODBC Driver Manager under the process context of the
    SQLExecutive process. Therefore, the process fails when the ODBC components are
    mismatched.

    WORKAROUND
    ==========

    To fix the version mismatch, perform the steps listed in the following article
    in the Microsoft Knowledge Base:

    Q170769 : PRB: "ODBC Resource DLL Is a Different Version Than ..."

    After installing the core components, you may want to check the SQL Executive
    process by doing the following:

    1. Open a command prompt and go to the MssqlBinn directory.

    2. Type the following command to run SQL Executive:

    sqlexec -c -v

    Verify that SQL Executive starts successfully. Press CTRL+C to close the
    command prompt.

    3. Start SQL Executive as a service and try to run a task.

    MORE INFORMATION
    ================

    It is also possible that while trying to apply cached operations from the
    Sqlcache.bin file, the service startup may time out. When you start SQL
    Executive from an application, it does not have the timeout limits as a service.
    If this is the case, you can either rename the Sqlcache.bin file to bypass the
    application of cached operations, or start from a command prompt first, to apply
    the cached operations without a timeout limit.

    Additional query words: access sqlexe dist repl failure structured query language exec

    ================================================== ====================
    Keywords : SSrvGen SSrvRep
    Version : WINNT:6.5
    Platform : winnt
    Issue type : kbprb
    ================================================== ===========================
    Copyright Microsoft Corporation 1999.






    ------------
    kevin at 3/30/00 10:43:30 AM

    What would cause this message to display or what does this mean??
    "Could not start the SQLServerAgent Service, error 2186, the service is
    not responding to the control function"



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •