Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Web Components Validation Failures RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    We have deployed an enterprise pool behind 2 load balancers are setup in their own little cluster so there will only be 1 logical load balancer.  We are having a problem during the second validation tests: the web components. 


    The error messages we are getting are basically all the same for all the web compoents. Connect failure. We did not get any errors for the first validation tests.

     

    Check Http URL   URL: https://OCSPOOL.XXXX.XXXX.COM/GroupExpansion/Int/service.asmx

    Internal Error: ConnectFailure

       Failure

    [0xC3FC200D] One or more errors were detected 

     

    Check Http URL   URL: https://OCSPOOL.XXXX.XXXX.COM/Abs/Int/Handler/F-0a38.dabs

    Internal Error: ConnectFailure

       Failure

    [0xC3FC200D] One or more errors were detected 

     

    Check Http URL   URL: https://OCSPOOL.XXXX.XXXX.COM/etc/place/null/slidefiles/blank.png

    Internal Error: ConnectFailure

       Failure

    [0xC3FC200D] One or more errors were detected 

     

    Could be be a problem with us giving the fqdn of the enterprise pool that has same name as the web farm?  Or could there be an issue with with the load balancer?  Thanks for any assistance

     

    Erik

    Saturday, March 1, 2008 5:01 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Configure the https certificate on the default web site of the web component server. Make sure ocspool.xxxx.xxxx.com

    is there as a subject name or in the SAN of the https certificate.

     

     

     

     

     

    R. Kinker
    MCSE 2003 (Messaging), MCTS - (LCS 2005, OCS 2007)
    http://www.ocspedia.com
    http://www.ITCentrics.com

    Sunday, March 2, 2008 6:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Good morning. Yes, we did configure the https certs on all four of the enterprise servers for ocspool.xxxx.xxxx.com. We are running enterprise edition in a consolidated deployment. We configured the certificates first through the install gui, then through the IIS admin program


    Erik

     

    Sunday, March 2, 2008 12:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I just double checked the ssl cert on the default website, and it looks good. The site is also enabled for ssl, it was not earlier so i checked it. However, I still couldnt get it to past the tests.  I don't know if this will do anything or not, but I cannot even get a webpage to come up when manually typing in that address in IE. Do you think there could be a problem with the load balancers?  Thanks


    Erik

     

    Monday, March 3, 2008 3:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    We have a load balance and had the exact same error.  We found that we had to add a registry entry:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
    3. Right-click MSV1_0, point to New, and then click Multi-String Value.
    4. In the Name column, type BackConnectionHostNames, and then press ENTER.
    5. Right-click BackConnectionHostNames, and then click Modify.
    6. In the Value data box, type the CNAME or the DNS alias, that is used for the local shares on the computer, and then click OK.
    Tuesday, February 3, 2009 6:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Do you already check port Availability?

     

    heres some of them

     Greets¡

    A load balancer is required in an Enterprise pool that has more than one Enterprise Edition Server. The load balancer performs the critical role of delivering scalability and high availability across multiple servers that are connected to a centralized database on the Office Communications Server, Back-End Database.

    Only one load balancer is required, but you can optionally create two logical load balancers—one for the Front End Servers and one for the Web Components Server—if you deploy Enterprise Edition in an expanded configuration. If you want to employ two logical load balancers, you can configure two virtual IP (VIP) addresses on one physical load balancer, or you can configure two separate physical load balancers.

    Note

    If you are deploying a pool that has a single Enterprise Edition server connected to the Back-End Database, skip to Step 3.2.


     

     

    Table 2 lists the ports that you must configure on the load balancer.

    Table 2. Required Ports on the Load Balancer Virtual IP Addresses

    Port Required

    Virtual IP

    Port Use

    5060

    Load balancer VIP used by the Front End Servers

    Client to server SIP communication over TCP

    5061

    Load balancer VIP used by the Front End Servers

    Client to Front End Server SIP communication over TLS

    SIP Communication between Front End Servers over MTLS

    135

    Load balancer VIP used by the Front End Servers

    To move users and perform other “pool” level WMI operations over DCOM

    444

    Load balancer VIP used by the Front End Servers

    Communication between the internal components that manage conferencing and the conferencing servers

    443

    Load balancer VIP used by the Web Components Server

    HTTPS traffic to the pool URLs

     

    When you configure the load balancer, you will need to ask the relevant network and DNS administrator for at least one virtual IP (VIP) address and FQDN for the load balancer (one for each logical load balancer), as well as a static IP address for every server that you plan to deploy in the Enterprise pool.

    Amado Imperial
    Tuesday, February 3, 2009 9:28 PM