Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Frontend Validation error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    I have install OCS 2007 on two servers with the following configuration:

     

    1) Front End, Web Conferencing, A/V Conferencing, Web Components and Archiving & CDR Server

    2) Access Edge Server, Web Conferencing Edge Server and A/V Edge Server

     

    When I run the Forent end validation, I get below mentioned report.

     

    Kindly help me in resolving the same

     

    Thanks,

    Amit

     

    Checking federation settings

     

    Default outgoing route for federation: None available
    Suggested Resolution: Federation is enabled at the forest level. However, no global or default federation servers are available. Ensure that these settings point to a valid server and that the server is running.

     

    Failure
    [0xC3FC200D] One or more errors were detected

     

    Checking global federation route

     

    Global Federation Route: ocspool.viteos.com
    Global Federation Route: The specified value equals the current server or pool.

     

    Warning
    [0x43FC200C] Not all checks were successful

    Checking local federation route

     

    Local Federation Route: ocspool.viteos.com
    Local Federation Route: The specified value equals the current server or pool.

     

    Warning
    [0x43FC200C] Not all checks were successful

    Checking static routes

     

    No WMI Instance Returned By Query : select * from MSFT_SIPRoutingTableData
    Static route: None Found

     

    Success

     

    Checking all trusted servers

     

     

     

    Failure
    [0xC3FC200D] One or more errors were detected

     

    Global Federation Route ocspool.viteos.com

     

    DNS Resolution succeeded: 10.1.0.145
    TLS connect succeeded: 10.1.0.145:5061
    Routing trust check and MTLS connectivity: Succeeded

     

    Success

    Local Federation Route ocspool.viteos.com

     

    DNS Resolution succeeded: 10.1.0.145
    TLS connect succeeded: 10.1.0.145:5061
    Routing trust check and MTLS connectivity: Succeeded

     

    Success

     

    Pool ocspool.viteos.com

     

    DNS Resolution succeeded: 10.1.0.145
    TLS connect succeeded: 10.1.0.145:5061
    Routing trust check and MTLS connectivity: Succeeded

     

    Success

    Attempting to send a CCCP HTTP request https://ocspool.viteos.com:444/LiveServer/Focus

     

    Received a successful HTTP response: HTTP Response: 200
    Content-Length:0
    Date:Thu, 14 Aug 2008 08:03:45 GMT
    Server:Microsoft-HTTPAPI/1.0

    Received a successful HTTP response: OK

     

    Success

     

    Internal Server vitsrvocs01.viteos.com

     

    DNS Resolution succeeded: 10.1.0.145
    TLS connect succeeded: 10.1.0.145:5061
    Routing trust check and MTLS connectivity: outgoing TLS negotiation failed; HRESULT=-2146893022
    Suggested Resolution: Routing trust check and/or MTLS connection establishment failed.
    This is usually caused by the remote server not accepting the certificate presented by the
    current machine. Check the local and remote server certificates for any
    misconfiguration. In addition, check whether the local server is recognized
    as a trusted server by the remote server.

     

    Failure
    [0xC3FC200D] One or more errors were detected

     

    Thursday, August 14, 2008 11:32 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Is your front-end server's hostname actually ocspool.viteos.com?  In a standard consolidated Front-End deployment the pool name is literally the server's FQDN.  Only an Enterprise deployment with mulitple Front-End servers uses a unique internal pool name.
    Thursday, August 14, 2008 7:33 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I think part of the problem there is you've specified the internal pool name as the global route for federation, meaning the pool is basically trying to connect to itself to send a federated message. You'll need to change that to be the internal FQDN of your Access Edge server.
    Friday, August 15, 2008 4:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We have Enterprise Edition of OCS 2007. I have installed OCS on 2 servers.

     

    1) Server name is vitsrvocs01.viteos.com and pool name is ocspool.viteos.com. I have enabled these features on this: Front End, Web Conferencing, A/V Conferencing, Web Components and Archiving & CDR Server

    2) The other server is called vitsrvmsg01.viteos.com and I have configure the other IP address on same network card as 10.1.0.176 and its FQDN is imsg.viteos.com. Following are the features on this server: Access Edge Server, Web Conferencing Edge Server and A/V Edge Server

     

    I hope you are clear with the setup.

     

    Friday, August 15, 2008 7:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    In the properties of the Front Ends I have mentioned the federation as the internal FQDN of the Edge Server (vitsrvmsg01.viteos.com) with port number 5061.

     

    Kindly help

     

     

    Friday, August 15, 2008 7:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Make sure that the following DNS entry is listed: http://www.microsoft.com/technet/prodtechnol/office/livecomm/library/deployse/lcsdse_8.mspx

     

    Tuesday, August 26, 2008 1:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes all the dns entries are already there. This error I get when I validate Front End from the OCS server. Internal clients are able to login and communicate. But I am not able to add & communicate with hotmail or yahoo user accounts.

    Tuesday, August 26, 2008 7:28 AM