Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
OCS Monitoring Agent - Service failed to start as requested. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    we setup the OCS Standard Server 2007 R2 just fine, but the Office Communications Server Monitoring Agent fails to start:

    Service Name: RtcQmsAgent
    Descriptive Name: Office Communications Server Monitoring Agent
    Failure
    [0xC3EC79E6] Service failed to start as requested.

    All other services work fine. No errors in the Application/System Log.

    Has anyone a hint?

    Thanks,
    Thomas



    Monday, February 9, 2009 3:48 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    This error comes from a missing prerequisite for the Monitoring Server role.

    Monitoring / Archiving both need MSMQ (Message Queueing) and unfortunately, Microsoft saw fit to start the Monitoring helper service by default regardless of whether you actually have a monitoring server in your environment - so if you don't have MSMQ you'll get that error message.

    If you don't want a monitoring server, simply deactivate that service altogether.. I haven't noted any negative sideffects.

    Regards
    Stephan
    • Marked as answer by hainzers Monday, February 9, 2009 9:28 PM
    Monday, February 9, 2009 4:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote


    The dependancy on the MSMQ services for OCS 2007 R2 update package has been removed with the June 2009 cumulative update (KB972041). This supercedes KB967831 released back in Apr 2009 (more here).

    Thanks for sharing with us if this helps.

    http://www.leedesmond.com
    Tuesday, June 30, 2009 10:27 AM
    Moderator

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote
    This error comes from a missing prerequisite for the Monitoring Server role.

    Monitoring / Archiving both need MSMQ (Message Queueing) and unfortunately, Microsoft saw fit to start the Monitoring helper service by default regardless of whether you actually have a monitoring server in your environment - so if you don't have MSMQ you'll get that error message.

    If you don't want a monitoring server, simply deactivate that service altogether.. I haven't noted any negative sideffects.

    Regards
    Stephan
    • Marked as answer by hainzers Monday, February 9, 2009 9:28 PM
    Monday, February 9, 2009 4:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks a lot for the information. That's reassuring.

    Regards,

    Thomas

     

    Monday, February 9, 2009 9:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for that bit of info. We saw this issue too last week and could not figure it out.

    I guess I'd have to ask why, if the MSMQ is needed, the setup does not tell us that? Or why, if monitoring is NOT included the agent is started up?

    I hope that this is fixed if/when MS put out SP1 for R2.
    Thomas Lee
    Sunday, March 1, 2009 12:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Negative side effect: if you disable the QoE Monitoring Agent Service, you'll be stuck when you'll want to install updates (esp QFE1 released in early April).

    The correct way is to install MSMQ on your Front-Ends, then if you have no QoE server, just leave everything that refers to QoE alone :p
    Benoit Boudeville - Avanade France & Belux http://unifiees.blogspot.com
    Monday, May 25, 2009 5:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    But, the worst fact is that yesterday's pack of KBs relating to PCS R2 got my machine stuck.
    Indeed, KB967831 triest to restart QoE service (even if NOT needed/required in my environment), then gives up and rolls back everything, thus leaving the system in an unstable situation, with the Fornt End Service NOT startable at all, whila ALL other services seem fine.

    Help please!

    -francesco
    Francesco Bosticco General HQ of Guardia di Finanza Datacenter Manager TAP since year 2000 ***
    • Proposed as answer by Francesco B_ Thursday, May 28, 2009 7:52 AM
    Thursday, May 28, 2009 7:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    UPDATE:

    http://blog.tiensivu.com/aaron/archives/1857-Office-Communications-Server-2007-R2-updates-April-2,-2009.html

    solves the question.
    All is now up and running!

    -francesco
    Francesco Bosticco General HQ of Guardia di Finanza Datacenter Manager TAP since year 2000 ***
    • Proposed as answer by Francesco B_ Thursday, May 28, 2009 7:54 AM
    Thursday, May 28, 2009 7:54 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Francesco,
    I just ran into this problem today when updating my OCS R2 server using Windows Update. KB 967831 failed. Now the Front End Service would NOT start. Could you be more specific about what must be done to have the FE service up and running again?

    Regards,
    Rune Flo

    Friday, June 5, 2009 9:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi RuneF


          Please check this link:
    http://blog.tiensivu.com/aaron/archives/1867-RtcQmsAgent-fails-to-start-on-OCS-2007-R2-server-and-causes-KB-967831-April-2009-update-for-Front-End-Server-components-install-to-fail.html

    http://social.microsoft.com/Forums/en-US/communicationsserversetup/thread/5d792086-6a39-4267-8e59-b1b8c69cb824

    Thanks

    Friday, June 5, 2009 9:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi RuneF,
    sharadsharma2k5 here below was quicker!
    And yes, Aaron's article (and entire blog) seems to be the best-of-breed for OCSR2 "real world" :)

    Short story, even if no pre-reqs or docs explicitly state it (unless you have to activate QoS roles), you'd have to install MSMQ services on each OCS FE server, autostart the relevant service, and nothing else.
    After that done, KB 967831 installs with no issues, and your OCS FE services will be healed.

    Thanks,
    francesco
    Francesco Bosticco General HQ of Guardia di Finanza Datacenter Manager TAP since year 2000 ***
    Saturday, June 6, 2009 12:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having a similiar problem.  I could not get the Telephony Conference, Monitoring Agent, or the Front End services to start. 

    After reading this forum, I decommissioned the Monitoring Agent service and then the Telephony Conference service started right up, but the Front End service will not start.  I still get the following error:  "Windows could not start the Office Communications Server Front-End on Local Computer.  For More information review the system event log.  If this is a non-microsoft service, contact the service vendor, and refer to service-specific error code -1007781418."

    I have tried to apply KB967831, but it will not complete because it is not able to start the Front End service. 

    Monday, June 8, 2009 6:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi JB3795


                 Can you please check the Office communciations Server Event logs and see if you have any other events?
    Check your Logon account is expired for OCS services?


    Thanks

    Monday, June 8, 2009 8:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I done this (install Message Queueing) but Monitoring Agent Service did not start, in fact, it starts but stops immediately with this message: "some services stop if there is nothing to do". 
    Also the Front-End Service starts, works por 5 minutes then stops. The update KB942872 is still waiting to install. I tried it many times but it doesn´t work.

    Anyone solved this problem?

    Monday, June 15, 2009 8:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote


    The dependancy on the MSMQ services for OCS 2007 R2 update package has been removed with the June 2009 cumulative update (KB972041). This supercedes KB967831 released back in Apr 2009 (more here).

    Thanks for sharing with us if this helps.

    http://www.leedesmond.com
    Tuesday, June 30, 2009 10:27 AM
    Moderator