locked
Web component deployment in an expanded configuration RRS feed

  • Question

  • We are testing with RTM code in an environment with one EE/Front End/Arch&CDR server, one Web Component server, and one Web Conf/Audio Video Conf server.  The shared folders for meeting presentations, metadata, and compliance and for ABS are located on a separate standalone server from the 3 servers outline above.

     

    Installation and activation for all OCS functionality completed successfully and IM and conferencing is working.  Except for the Web component functionality pieces.  These do not work unless I explicitly enter the name of the server the compoents reside on.

     

    Based on the planning guide, IIS is not required on the Enterprise Edition server on the front end server in an expanded configuration - only those servers operating as the web components.  But the URL errors and it appears that the Front End server doesn't seem to "forward" the request to the Web components server.  The error received on the Web Comp validation is

    URL: https://OCSPool01.<fqdn>/GroupExpansion/Int/service.asmx
    Internal Error: ConnectFailure
      Failure
    [0xC3FC200D] One or more errors were detected

     

    Has anyone implemented Web Components on an expanded configuration?  Have you had similar issues?

    Tuesday, October 9, 2007 11:18 PM