locked
Please !! Error: DataMCUSvc(1632) failed to send health notifications to the MCU factory RRS feed

  • Question

  • Hi guys!!

    I cannot sign in to Communicator , and i can't start frontend services. OCS was ok untill friday, and now i've got that error, i really don't know why.

    "The process DataMCUSvc(1632) failed to send health notifications to the MCU factory at https://poste01.MOCS.niji.local:444/LiveServer/MCUFactory/.

    Failure occurrences: 257, since 8/6/2007 12:10:29 PM."

     

    (poste01.MOCS.niji.local is my OCS frontend server.)

     

    Please, help me !!


     

    Monday, August 6, 2007 12:02 PM

All replies

  • does someone have an idea?
    Someone had the same issue but no responses: http://forums.microsoft.com/Ocs2007publicbeta/ShowPost.aspx?PostID=1410441&SiteID=57

    please!!!!!
    Tuesday, August 7, 2007 1:06 PM
  • Can you let us know the status of your issue? Can you share your solution if you have one? If not, please let us know what else you have tried.

    Tuesday, December 18, 2007 5:50 PM
  • We have recently seen the same error.  Right after the MS update was automatically applied last night, the server was automatically rebooted and when it came back up, the Front End Service did not start, but everything else started.  Looking through the event log, it appears that the front-end service is dependent upon other OCS services starting successfully.  This is what I see as the critical path of failure for the Front-End service not starting from the event log on my server.  It appears OCS Services are attempting to start before basic communications services (like NETLOGON) have successfully started. 

     

     

    Event Type: Information
    Event Source: OCS Server
    Event Category: (1000)
    Event ID: 12289
    Date:  1/10/2008
    Time:  7:47:36 AM
    User:  N/A
    Computer: OCS
    Description:
    The service was stopped.


    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    Event Type: Error
    Event Source: OCS Server
    Event Category: (1000)
    Event ID: 12321
    Date:  1/10/2008
    Time:  7:47:35 AM
    User:  N/A
    Computer: OCS
    Description:
    Unable to initialize the registration component. The service has to stop.

    Error code:800706FD (The trust relationship between this workstation and the primary domain failed.
    ).

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Error
    Event Source: OCS User Services
    Event Category: (1006)
    Event ID: 30912
    Date:  1/10/2008
    Time:  7:47:35 AM
    User:  N/A
    Computer: OCS
    Description:
    Initialize failure. Failed to initialize the Notify component.
    Error code: 800706FD

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: OCS Data MCU
    Event Category: (1018)
    Event ID: 41063
    Date:  1/10/2008
    Time:  7:47:21 AM
    User:  N/A
    Computer: OCS
    Description:
    Could not connect to Active Directory to read configurations settings. Will retry in 30 seconds.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Error
    Event Source: OCS WMI Event Provider
    Event Category: (1027)
    Event ID: 56008
    Date:  1/10/2008
    Time:  7:47:21 AM
    User:  N/A
    Computer: OCS
    Description:
    The WMI event provider could not detect the back-end database associated with this pool. Verify that all server roles are activated and that network connectivity exists to AD.


    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Error
    Event Source: OCS WMI Consumer
    Event Category: (1002)
    Event ID: 20491
    Date:  1/10/2008
    Time:  7:47:21 AM
    User:  N/A
    Computer: OCS
    Description:
    Server could not retrieve information from Active Directory.

    HRESULT: 0x0x8007054B
    Cause: This could happen if the domain controller and /or global catalog are not functional or cannot be contacted, or if permissions to the service account are altered.
    Resolution:
    Make sure that connection to Active Directory is functional and the account the service is running under has proper privileges.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Information
    Event Source: OCS Server
    Event Category: (1000)
    Event ID: 12287
    Date:  1/10/2008
    Time:  7:47:21 AM
    User:  N/A
    Computer: OCS
    Description:
    The service is starting.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: OCS IM MCU
    Event Category: (1019)
    Event ID: 33012
    Date:  1/10/2008
    Time:  7:47:20 AM
    User:  N/A
    Computer: OCS
    Description:
    Office Communications Server IM MCU Service startup is delayed due to errors in initializing WMI. Startup will be retried in 30 seconds

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61032
    Date:  1/10/2008
    Time:  7:47:20 AM
    User:  N/A
    Computer: OCS
    Description:
    Error:Failed to access wmi at start service, retrying

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    I hope this helps other folks and hopefully Microsoft diagnose and correct the issue without the end user having to manually modify service dependencies in the registry.  I may try making RTCsrv start dependent upon NETLOGON and see if that makes a difference.

     

    Mike

    Thursday, January 10, 2008 1:13 PM
  • OK.  Here are the results:

     

    After making Rtcsrv service startup dependent on Netlogon service start, no change in any error log messages.  Then after another careful look at the event log, I decided to make Netlogon dependent on Dnscache (DNS client service) start. this cleared the inital failures at the beginning of the log, but the following three errors and one major event keep happening:

     

    In the Application log:

    Event Type: Error
    Event Source: Userenv
    Event Category: None
    Event ID: 1053
    Date:  1/10/2008
    Time:  8:49:10 AM
    User:  NT AUTHORITY\SYSTEM
    Computer: OCS
    Description:
    Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

     

    This is usually related to the Netlogon service starting without DNS being available, but in this case it is/should be due to the dependency of Netlogon to the DNS Client.

     

    in the OCS log:

     

    Event Type: Error
    Event Source: OCS User Services
    Event Category: (1006)
    Event ID: 30912
    Date:  1/10/2008
    Time:  8:49:26 AM
    User:  N/A
    Computer: OCS
    Description:
    Initialize failure. Failed to initialize the Notify component.
    Error code: 800706FD

     

     

    Event Type: Error
    Event Source: OCS Server
    Event Category: (1000)
    Event ID: 12321
    Date:  1/10/2008
    Time:  8:49:26 AM
    User:  N/A
    Computer: OCS
    Description:
    Unable to initialize the registration component. The service has to stop.

    Error code:800706FD (The trust relationship between this workstation and the primary domain failed.
    ).

     

    And subsuquently the OCS Service is stopped.

     

    Event Type: Information
    Event Source: OCS Server
    Event Category: (1000)
    Event ID: 12289
    Date:  1/10/2008
    Time:  8:49:27 AM
    User:  N/A
    Computer: OCS
    Description:
    The service was stopped.


    Then all the OCS MCU Infrastructure services failed to send health notifications to the MCU factory.

     

    If anyone has any ideas, that would be great.

     

    Thanks,

     

    Mike

    Thursday, January 10, 2008 2:20 PM
  •  

    Hello,

     

    Have you found the solution to this problem?

     

    I am getting the same issue myself.

     

    Thank you,

     

    Dimitris.

    Saturday, February 9, 2008 10:26 PM
  • What results do you get when you run validations on the Front end and Web components? This will usually give you more of an indication of what is going on.

     

    Monday, February 11, 2008 12:24 AM
  • Hey,

    Since one year, does any one have the solution to this problem ?

    I have the same problem with one FE and no load balancer.

    Thank you
    Thursday, June 19, 2008 1:31 PM
  • I am having the same issue now!  We completed a fresh install of OCS Standard 2 days ago. 


    The system/OCS was operating fine this morning and the health check returned positive results (with the exception of one .NET critical hotfix).

     

    MS updates that were applied today were:

    kb945055

    kb945172

    kb948109

    akonix plug-in

     

    Finally, I ended up calling MS.  The MS tech and I tried recreating the certificate, switching ports for the front end service (5060/TCP), and adding the OCS domain service accounts to the local admin group (based upon other cases).  After running the best practice analyzer again, it again stated that an important hotfix is available (hotfix 923028). We attempted to run this update, but it failed stating that the platform was not a supported version.  I checked the windows installer, and it is the most up-to-date. Furthermore, if you read the MS forums below, you'll notice reference to these errors would be related to FQDN edge server entries.  This configuration does not have a single FQDN entry related to federation or edge servers, so we're safe there.  The MS tech was not able to solve the issue.


    Any thoughts?  I have found numerous posts, and the possible "solutions" are inconsistant and rather odd...


    Event errors are below...


    Application Event Log
    Event Type:    Error
    Event Source:    .NET Runtime 2.0 Error Reporting
    Event Category:    None
    Event ID:    5000
    Date:        7/31/2008
    Time:        4:50:29 PM
    User:        N/A
    Computer:    server
    Description:
    EventType clr20r3, P1 rtchost.exe, P2 3.0.6362.0, P3 46a4cc79, P4 microsoft.rtc.server.mcuinfrastructure, P5 3.0.0.0, P6 46a4cc06, P7 1aa4, P8 0, P9 exception, P10 NIL.


    System Event Log
    Event Type:    Error
    Event Source:    Service Control Manager
    Event Category:    None
    Event ID:    7024
    Date:        7/31/2008
    Time:        4:55:00 PM
    User:        N/A
    Computer:    server
    Description:
    The Office Communications Server Front-End service terminated with service-specific error 3287447050 (0xC3F2760A).

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Event Type:    Error
    Event Source:    Schannel
    Event Category:    None
    Event ID:    36870
    Date:        7/31/2008
    Time:        4:16:28 PM
    User:        N/A
    Computer:    server
    Description:
    A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from the cryptographic module is 0x80090016.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    OCS Event Log
    Event Type:    Error
    Event Source:    OCS MCU Infrastructure
    Event Category:    (1022)
    Event ID:    61013
    Date:        7/31/2008
    Time:        4:56:21 PM
    User:        N/A
    Computer:    server
    Description:
    The process AcpMcuSvc(2436) failed to send health notifications to the MCU factory at https://server.domain.com:444/LiveServer/MCUFactory/.
    Failure occurrences: 5, since 7/31/2008 4:55:21 PM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



    Event Type:    Error
    Event Source:    OCS MCU Infrastructure
    Event Category:    (1022)
    Event ID:    61013
    Date:        7/31/2008
    Time:        4:56:18 PM
    User:        N/A
    Computer:    server
    Description:
    The process IMMcuSvc(1656) failed to send health notifications to the MCU factory at https://server.domain.com:444/LiveServer/MCUFactory/.
    Failure occurrences: 5, since 7/31/2008 4:55:18 PM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



    Event Type:    Error
    Event Source:    OCS Snap-in
    Event Category:    (1004)
    Event ID:    30710
    Date:        7/31/2008
    Time:        4:55:01 PM
    User:        N/A
    Computer:    server
    Description:
    Office Communications Server Snap-in failed to start service:
     Service Name = RTCSRV
      
     HRESULT = 0x8007042A
     Error Description = The service has returned a service-specific error code.


    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.




    Event Type:    Error
    Event Source:    OCS Server
    Event Category:    (1000)
    Event ID:    12308
    Date:        7/31/2008
    Time:        4:54:59 PM
    User:        N/A
    Computer:    server
    Description:
    A component could not be started.  The service has to stop.

    Component: Live Communications Applications Module  Error code: C3F2760A (Failed to start all critical applications

    Cause: One or more critical applications failed to register within the maximum allowable time, which is (60 + (30 * n)) seconds where n is the number of critical applications.
    Resolution:
    Examine the list of enabled critical applications via the MMC snap-in.  Examine the event log entries before this one to determine which critical applications successfully registered with the server.  Those that did not register successfully with the server within the                maximum allowable time are the ones causing this error.)

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



    Event Type:    Error
    Event Source:    OCS Applications Module
    Event Category:    (1010)
    Event ID:    30218
    Date:        7/31/2008
    Time:        4:54:59 PM
    User:        N/A
    Computer:    server
    Description:
    Failed to start all critical applications

    Cause: One or more critical applications failed to register within the maximum allowable time, which is (60 + (30 * n)) seconds where n is the number of critical applications.
    Resolution:
    Examine the list of enabled critical applications via the MMC snap-in.  Examine the event log entries before this one to determine which critical applications successfully registered with the server.  Those that did not register successfully with the server within the                maximum allowable time are the ones causing this error.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



    Event Type:    Warning
    Event Source:    OCS Applications Module
    Event Category:    (1010)
    Event ID:    30232
    Date:        7/31/2008
    Time:        4:51:29 PM
    User:        N/A
    Computer:    server
    Description:
    Office Communications Server startup is pending.

    Some configured critical applications have not yet registered.
    Resolution:
    For script only applications ensure that the application is available in the path specified in the MMC, and that no errors are reported by the Office Communications Server Script-Only Applications Service. For non-script only critical applications ensure that they are configured to register on server startup.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



    Event Type:    Error
    Event Source:    OCS AppDomain Host Process
    Event Category:    (1029)
    Event ID:    50007
    Date:        7/31/2008
    Time:        4:50:29 PM
    User:        N/A
    Computer:    server
    Description:
    An unhandled exception was encountered.

    Exception Details. System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.Rtc.Server.McuFactory.McuFactoryHost.Main(String[] args)
       at Microsoft.Rtc.Server.McuFactory.ExecutableEntryPoint.Main(String[] args)
       at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
       at System.AppDomain.ExecuteAssemblyByName(String assemblyName, Evidence assemblySecurity, String[] args)
       at System.AppDomain.ExecuteAssemblyByName(String assemblyName, Evidence assemblySecurity, String[] args)
       at Microsoft.Rtc.AppDomainHost.Launcher.AppDomainLauncher.RunThread()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    Resolution:
    Restart the server. If the problem persists contact product support.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Friday, August 1, 2008 4:10 AM
  •  

    Update:

     

    I do not know the true cause to this problem or the true solution to this problem.  However, I fixed our issue.

     

    First, I deactivated the OCS SE services (in particular order below)

    A/V

    Web Conf

    Web Components

    Front End (make sure your users are not enable or associated to the OCS SE pool in AD.  If so, the wizard will fail or you will be end forcing the wizard to complete)

     

    Second, uninstall OCS SE services (add/remove programs)

     

    A/V

    Web Conf

    Standard Edition

     

    Third, wait for AD to replicate the changes (typically 15-60mins).

     

    Fourth, reinstall OCS SE.

     

    Seems to work now...

    Friday, August 1, 2008 7:20 PM
  • I can't tell you why I had this issue, but I can tell you what I did that made it go away.

     

    I deactivated Web Components, A/V and Web Conferencing.  Then I allowed AD to replicate.  Restarted the OCS install and went back in to configure those same pieces.  Once done, I restarted the services through the setup program.

     

    I received the errors for about 10 minutes, then they quit.  AD replication latency?  Either way, I seem to be error free at the moment.  Wish I knew the actual cause/fix.

    Thursday, August 7, 2008 7:48 PM
  • Just got the same problem. But have solved it, it's because the password for RTCService account has expired.

    Try to make "password never expires" for the account and restart the Front End Services.
    Tuesday, September 9, 2008 5:17 AM
  • i had a same problem about this trouble but i correct this trouble with RCTService user account password reset and restart the Office Communications Server Front-End,Office Communications Server IM Conferencing,Office Communications Server Telephony Conferencing,Office Communications Server Web Conferencing services...

    Yunus DERVİŞ
    Türkiye/ANKARA
    Friday, June 19, 2009 9:09 AM