CA Automation Point

CA Automation Point Tech Tip: How to resolve "Switch from current encoding to specified encoding not supported" HTTP/1.1- 500 error (Web Services Request)

  • 1.  CA Automation Point Tech Tip: How to resolve "Switch from current encoding to specified encoding not supported" HTTP/1.1- 500 error (Web Services Request)

    Posted 06-19-2015 10:11 AM

    Issue/Problem:

    When you try to communicate to another server that has been setup for web services with Tomcat the attempt is failing. You find the following message in the RequestService.log file, wrapped in XML tags:

     

    "Failed to read XML data from a stream, error on line 1: (0xc00ce56f) Switch from current encoding to specified encoding not supported."You will also notice a HTTP1.1 500 error (internal server error)."

     

    Root Cause:

    You are using an 11.4.1.0 (or later release) RequestService (Web Services) client with an 11.4.0.0 server; development released some updates in 11.4.1 to better handle character encoding soon after 11.4 went GA, so the older Web Services server cannot interpret the updated character encodings sent by the updated WS client.

     

    Solution:

    You will needs to upgrade to at least 11.4.1.0 (SP1) on the AP Server that is running the Web Services listening and serving the client requests; alternatively, you can downgrade the RequestService client on the remote system whose making the web service request to 11.4.0.0. You can find the RequestServiceClientDist.zip in the %AP_HOME%\Sample\websvc directory. Follow the instructions here to install the RequestService client on your remote system: