locked
Office Communications Server IM MCU Service could not be started. RRS feed

  • Question

  • Hi!

    When trying to start the  Office Communications Server IM Conferencing service, I get the following error to event log:

    Office Communications Server IM MCU Service could not be started.

    Message: Value cannot be null.
    Parameter name: listeningUrl
    Stack:    at Microsoft.Rtc.Server.McuInfrastructure.HttpTransport..ctor(String listeningUrl, ICccpConfigurationProvider config, XmlWriterSettings writerSettings)
       at Microsoft.Rtc.Server.McuInfrastructure.CccpAdapter..ctor(String listenerUri, ICccpConfigurationProvider config)
       at Microsoft.Rtc.Server.McuInfrastructure.LsServiceProvider.GetMcuCccpAdapter()
       at Microsoft.Rtc.Server.McuInfrastructure.ServiceProvider.get_CccpAdapter()
       at Microsoft.Rtc.Server.McuInfrastructure.ServiceProvider.GetService(Type interfaceType)
       at Microsoft.Rtc.Server.McuInfrastructure.RootServiceProvider.GetService[T]()
       at Microsoft.LiveServer.ImMcu.ConferenceManager.InitializeCccpAdapter()
       at Microsoft.LiveServer.ImMcu.ConferenceManager..ctor()
       at Microsoft.LiveServer.ImMcu.ImMcuService.CreateConferenceManager()
       at Microsoft.Rtc.Server.McuInfrastructure.RetryLogicHandler`1.ExecuteMethod(RetryableMethodDelegate retryableMethod, TimeSpan retryPeriod, TimeSpan maxDuration)
       at Microsoft.LiveServer.ImMcu.ImMcuService.OnStart(String[] args)

    Cause: Startup errors.
    Resolution:
    Check the events prior to this to resolve the service startup issue.

    For more information, see Help and Support Center at


    The same type of error comes for Telephony conferencing.

    Front-end service is starting fine.

    I had to change the name of the OCS server and reinstall OCS and after that these two services don't start anymore. Could it be that there are some settings in the AD from the previous installation that are causing these problems?

    -- Ville
    Wednesday, March 11, 2009 1:18 PM

All replies

  • I have similar issue.  I rebuilt OCS2007 SE with new name etc.  In the deployment log I have:

    Office Communications Server 2007 Deployment Log
    Time Logged: May 23, 2009 11:01:13 PM Expand AllCollapse All

    Action Action Information Execution Result
    Execute Action       Failure
    [0xC3EC79E6] Service failed to start as requested.
    Starting Service   Service Name: RTCSRV
    Descriptive Name: Office Communications Server Front-End
    Service Status: Already running
      Success
    Starting Service   Service Name: RTCACPMCU
    Descriptive Name: Office Communications Server Telephony Conferencing
    Service Status: Already running
      Success
    Starting Service   Service Name: RTCIMMCU
    Descriptive Name: Office Communications Server IM Conferencing
    Service Status: Already running
      Success
    Starting Service   Service Name: RTCDATAMCU
    Descriptive Name: Office Communications Server Web Conferencing
    Service Status: Already running
      Success
    Starting Service   Service Name: RTCAVMCU
    Descriptive Name: Office Communications Server Audio/Video Conferencing
    Service Status: Error
      Failure
    [0xC3EC79E6] Service failed to start as requested.
    Office Communicator Event Log says:

    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61031
    Date:  23/05/2009
    Time:  11:01:17 PM
    User:  N/A
    Computer: SESERVER
    Description:
    Failed to start service for the following reasons Value cannot be null.
    Parameter name: listeningUrl

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

    Sunday, May 24, 2009 6:11 AM