Content Management and Capture

 View Only
  • 1.  Webclient cannot be established error in Filenet ACCE

    Posted Mon February 19, 2024 11:40 AM

    When attempting to access the FileNet ACCE URL and fetching documents or browsing, we encounter an unusual "a connection to the webclient cannot be established by using the Following url" error Additionally, when developer tools are enabled in the browser, a "net::ERR_SSL_PROTOCOL_ERROR" is observed. What could be the reason for the occurrence of this error? 



    ------------------------------
    Haresh Rajagopal
    ------------------------------


  • 2.  RE: Webclient cannot be established error in Filenet ACCE

    Posted Tue February 20, 2024 01:27 AM

    Is it intermittent? Or always happened? Generally, this is caused by the https connection between browser and web/app server. And it is not application related. Recently I know about a similar intermittent issue, which is caused by IHS version need to be upgrade for latest browsers(Chrome and Edge) SSL connection enhancement. 

    So I'd suggest to check:

    1. Which browser is issued?
    2. The web server type and version 

    And may need to contact the web server product.



    ------------------------------
    JIE ZHANG
    ------------------------------



  • 3.  RE: Webclient cannot be established error in Filenet ACCE

    Posted Tue March 12, 2024 10:47 AM

    Hi Jie,

    Thanks for the reply. We are using Edge browser while ACCE URL and the Web Server version is IBM HTTP Server 8.5.5.14. Yes its a intermittent issue and its occurring only when we use IHS ACCE URL and Yes, its not application related. Any idea How did they resolve the issue? As even after enabling the trace we are unable to debug this issue.
    Can you provide any suggestion on this. 



    ------------------------------
    Haresh Rajagopal
    ------------------------------



  • 4.  RE: Webclient cannot be established error in Filenet ACCE

    Posted Wed March 13, 2024 02:55 AM

    Hi Haresh,

    In that case, WAS team helped to found that the IHS needs to be upgrade. There is an issue with latest Chrome/Edge (browser new logic) with old IHS. I checked the history, that the IHS version was upgraded from 9.0.0.10(out of support) to 9.0.5.18.  The WAS support expert suggested to upgrade to the latest IHS ifix if it is not out of support. 



    ------------------------------
    JIE ZHANG
    ------------------------------