locked
Validation - A/V - MCU Connectivity ReceiveFailure RRS feed

  • Question

  • Hello,

    I keep having problems wit the MCU using OCS 2007 trial.
    I kan use the office communicator, but i can not get live meetings to work.
    The installation of OCS goes OK but the validation fails. See the error below.
    It looks like a certificate problem but I can not figure out what goes wrong.

    I have tried:
    - reinstall OCS from the ground up (5 times) using OCS_StandardEditionDeployment.doc
    - VMware server
    - Windows 2003 Standard Edition
    - SQL Server 2005 developer edition
    - Office Communication server 2007 Standard Edition trial
    - unprep the forest and domain (tip in other forum post)
    -
    using diferent machine names (tip in other forum post)
    - using diferent certifictes from diferent vendors.
    - uninstalling / installing dataMCU
    - uninstalling / installing IIS
    - puting sites on different ports
    - installing or not installing all microsoft updates
    - removing all unnecessery root certificats (tip in other forum post)

    In the event log I am now seeing the following errors:
    The process IMMcuSvc(3644) failed to send health notifications to the MCU factory at https://OCS.manpower.dev:444/LiveServer/MCUFactory/.
    Failure occurrences: 5, since 14-10-2008 11:41:24.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    The process AVMCUSvc(2116) did not receive a certificate from the client.

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

    Here is the message that i get using the Validation wizards:

    Validation – Front End Server

    Execute Action

    Diagnose Server

    Check Configuration

    Test Conference

    Validate Conference Scheduling and Joining

    Join Conference

    Collaboration Activity Participate

    MCU: chat

    Failure

    [0xC3EC79FC] One or more validation errors occurred. 

     

     

    Validation – A/V

    Execute Action

    Diagnose MCU

    Check Connectivity

    Check MCU Connectivity

    URL: https://OCS.manpower.dev:444/LiveServer/AVMCU/

    HTTP Connectivity Error : ReceiveFailure

    HTTP Connectivity Error : Receive failure typically indicates that the connection was closed by the remote host. This can happen if the remote server does not trust the certificate presented by the Local Server.

     

    HTTP Connectivity Error : Ensure that the certificate of the local server and remote server are bothvalid, have not expired, and contain valid subject name. In addition, ensure that the certificate chain of both Server(s) are valid. Ensure that the certificate chain of the local server is installed on the remote server and vice-versa. The most up-to date certificate chain that was used to issue the server certificate must be present.

    Failure

    [0xC3FC200D] One or more errors were detected

    Check MCU Factory Connectivity

    MCU Type: audio-video

    URL: https://OCS.manpower.dev:444/LiveServer/MCUFactory/

    HTTP Connectivity Error : ReceiveFailure

    HTTP Connectivity Error : Receive failure typically indicates that the connection was closed bythe remote host. This can happen if the remote server does not trust the certificate presented by theLocal Server.

     

    HTTP Connectivity Error : Ensure that the certificate of the local server and remote server are bothvalid, have not expired, and contain valid subject name. In addition, ensure that the certificate chainof both Server(s) are valid. Ensure that the certificate chain of the local server is installed on the remote server and vice-versa. The most up-to date certificate chain that was used to issue the server certificate must be present.

    Failure

    [0xC3FC200D] One or more errors were detected


    Tuesday, October 14, 2008 9:49 AM

All replies

  •  

    Verify that you have your A/V authentication port set to 444.  Default is 5062.  You can check this under pool -> Properties -> A/V Conferencing

     

    Wednesday, October 15, 2008 2:22 PM
  • An A/V authentication port can only be selected if there is a edge server installed. I do not have an edge server.
    I have searched for other posts about this and i found some comment saying that you don't have to select an authentication port if you don't use an edge server.

    I did tried adding the logical information for an edge server using:

    Forest, Global Properties, Edge Servers, A/V Edge Server.

    Specify the internal FQDN and port used for the A/V Authentication Service for each A/V Edge Server in your deployment

    I added the ocs server with port 444

    After that I am able to select this as an authentication server.

    But the error remains the same.


    So I still have no clue what to do next. I think i will try installing everything again from the ground up and then try the enterprise edition instead of the standard edition. May using a different setup will suddenly solve everything for me.

    Monday, October 20, 2008 7:04 AM
  • Just a thought. are you connecting with Live Meeting to the OCS frontend server from a network that is behind a firewall via NAT (or from a network with a different IP range)? If so you defenitely need to deploy the Edge Server as well. Read the following document to get a better understanding on the Edge topologies:  http://www.microsoft.com/downloads/details.aspx?familyid=e4a8d703-e41a-47d9-b9dd-2799f894af92&displaylang=en

     

    Try to connect with the live meeting client from the internal OCS (frontend) server.  If that works you can be sure that the basic frontend server configuration is OK.

     

    /Thomas

     

    Monday, October 20, 2008 1:56 PM
  • Did you ever solve this?  I have the same problem.
    Monday, March 16, 2009 7:22 PM
  • No, I was unable to solve this problem. We stopped using OCS.
    Monday, March 30, 2009 10:31 AM