locked
SQLSERVERAGENT (SQLSERVERAGENT) service is not running on the server RRS feed

  • Question

  •  

    hi guys,

    i really need your help.

    I try to install CRM 2011 but i get the following error "SQLSERVERAGENT (SQLSERVERAGENT) service is not running on the server ..." on system check page. it's quite confusing, because i have checked and re-checked the sql server agent services is running (started).

    Here are the scenarios :

    AD, CRM, and SQL are installed on separated server.

     

    AD :

    * OS : windows server 2008 R2 ent 64 bit.

    CRM Server :

     

    * OS : windows server 2008 R2 ent 64 bit.

    * CRM : CRM 2011

    SQL :

    * OS : windows 2003 enterprise edition

    * SQL Server 2008 R2 64  bit

    Below is the log :

    13:25:43|   Info| Check IisAdminServiceValidator: Success
    13:25:43|   Info| Check W3svcServiceValidator: Success
    13:25:43|   Info| Group Microsoft SQL Server™
    13:25:43|  Error| Check SqlServerAgentValidator : Failure: SQLSERVERAGENT (SQLSERVERAGENT) service is not running on the server xxxxx.
    13:25:43|   Info| Group Microsoft SQL Server Reporting Services
    13:25:43|   Info| Check ReportingUrlValidator: Success
    13:25:44|   Info| Check ExistingRSValidator: Success
    13:25:44|   Info| Group Active Directory®
    13:25:44|   Info| Check DomainUserValidator: Success
    13:25:44|Verbose| Validation ran.
    13:25:44|Verbose| Validation completed.


    Thanks in advanced.

     

    n. b: sorry i am new bie. Remind me if i do post in a wrong thread.

     

    Tuesday, July 12, 2011 7:52 AM

Answers

  • Hello Hery,

    Check if the SQL Server Agent is started: Start > Run > services.msc > SQL Server Agent (instance_name) > right-click & Start. You should also set it on Automatic if it's not.

    Also, take a look at this post: http://technet.microsoft.com/en-us/library/ms191454.aspx.


    Cornel Croitoriu - Senior Software Developer

    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Biz-Forward.comCroitoriu.NET

    • Marked as answer by hery halim Friday, July 15, 2011 6:35 AM
    Tuesday, July 12, 2011 8:07 AM
  • also, try cycling the servince and restarting it to see if it helps.

    And make sure in the installation wizard that you really are pointing to the SQL server you think you are.


    Jamie Miley
    Check out my about.me profile!
    http://mileyja.blogspot.com
    Linked-In Profile
    Follow Me on Twitter!

    • Marked as answer by hery halim Friday, July 15, 2011 6:35 AM
    Tuesday, July 12, 2011 3:56 PM
    Moderator
  • hi cornel, jamie..

    thanks for you quick replies.

    i re-check the sql server version again with the client and find out, they use the 32-bit sql server 2008 r2 ent, not 64-bit.

    that should be the problems.

     

    Anyway,thanks for your help.

     

     

    • Marked as answer by hery halim Friday, July 15, 2011 6:37 AM
    Friday, July 15, 2011 6:37 AM

All replies

  • Hello Hery,

    Check if the SQL Server Agent is started: Start > Run > services.msc > SQL Server Agent (instance_name) > right-click & Start. You should also set it on Automatic if it's not.

    Also, take a look at this post: http://technet.microsoft.com/en-us/library/ms191454.aspx.


    Cornel Croitoriu - Senior Software Developer

    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Biz-Forward.comCroitoriu.NET

    • Marked as answer by hery halim Friday, July 15, 2011 6:35 AM
    Tuesday, July 12, 2011 8:07 AM
  • also, try cycling the servince and restarting it to see if it helps.

    And make sure in the installation wizard that you really are pointing to the SQL server you think you are.


    Jamie Miley
    Check out my about.me profile!
    http://mileyja.blogspot.com
    Linked-In Profile
    Follow Me on Twitter!

    • Marked as answer by hery halim Friday, July 15, 2011 6:35 AM
    Tuesday, July 12, 2011 3:56 PM
    Moderator
  • hi cornel, jamie..

    thanks for you quick replies.

    i re-check the sql server version again with the client and find out, they use the 32-bit sql server 2008 r2 ent, not 64-bit.

    that should be the problems.

     

    Anyway,thanks for your help.

     

     

    • Marked as answer by hery halim Friday, July 15, 2011 6:37 AM
    Friday, July 15, 2011 6:37 AM