Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Error messages for remote case types

Updated on March 29, 2022

If any issues connected with remote case types occur, analyzing error messages helps you understand the cause of the issue and then make informed decisions about how to fix the issue. The JSON response to an issue includes relevant information that you can use when troubleshooting remote case types.

JSON response

The following JSON response is common to all issues connected to remote case types that might occur in your system:

{
   "errorClassification":"error classification",
   "localizedValue":"the root cause of the issue",
   "errorDetails":[
      {
         "message":"error message type",
         "erroneousInputOutputFieldInPage":"",
         "erroneousInputOutputIdentifier":"",
         "errorClassification":"",
         "localizedValue":"The error message that an application displays at run time.",
         "messageParameters":[
            
         ]
      }
   ]
}

The following JSON response includes the details of a sample execution error:

{
   "errorClassification":"Execution error",
   "localizedValue":"Exception while getting access token",
   "errorDetails":[
      {
         "message":"Error_Execution_Error",
         "erroneousInputOutputFieldInPage":"",
         "erroneousInputOutputIdentifier":"",
         "errorClassification":"",
         "localizedValue":"Error while executing request. Please contact administrator.",
         "messageParameters":[
            
         ]
      }
   ]
}

Logs in fixing issues

Ensure that you enable logs so that you can obtain additional details about issues that might occur in your system. For remote case types, ensure that you enable RemoteWebGatewayImpl and com.pega.platform.web.gateway.validations. For more information, see Log files tool.

Incoming requests errors

The following table lists the errors that are related to processing incoming requests in the consumer system:
The root cause of the issue in JSONReason for the error messageSteps to fix the issue
Invalid tenant hash in the input URLTenant hash in the URL of the producer system is invalid.Check the tenant hash in the URL of the producer system that you provide when you create a remote case type or update remote case type details.
Invalid requestThe AAT cookie or the JWT token is invalid.Ensure that required credentials are present and correct in the request.
Expired JWT TokenThe JWT token that you use is expired.Enable logs and contact Pega Support.
Empty remote system ID in the requestThe remotesystemid header is empty in the request.Verify that the remotesystemid header is present in the request.
Remote system details do not existThe data-admin-remotesystem data instance is empty in the remotesystemid element of the request.Verify that the data-admin-remotesystem data instance that corresponds to the remotesystemid element exists in your system and is correct.
AAT cookie not found in the requestThe AAT cookie is missing from the request.Verify that the AAT cookie is part of the request.
Invalid AATThe exception while processing the incoming AAT token occurred.Enable logs, contact your security team, and contact Pega Support.
Invalid URI requestURI in the remote system details is invalid.Verify that the URI of the remote system that you provide when you configure the consumer system is correct.
Invalid request methodThe REST calls do not support the requested HTTP method.Ensure that you invoke only the supported HTTP methods.
Invalid CSRF TokenThe CSRF token is invalid.Enable logs, contact your security team, and contact Pega Support.
AAT Cookie is not parsed successfullyThe system is unable to parse the incoming AAT cookie.Enable logs, contact your security team, and contact Pega Support.

Gateway processing errors

The following table lists errors that are related to gateway processing exceptions:
The root cause of the issue in JSONReason for the error messageSteps to fix the issue
Exception when write stream from remote response to servlet responseException occurred while streaming a response from the remote system.Enable logs and contact Pega Support.
Exception while firing the remote requestNot applicable.Enable logs and contact Pega Support.
Connection pool shutdown while firing the remote requestThe dynamic system setting for connection pool changed during request processing, and the request processing failed.After you save the dynamic system setting with the new value, restart the request that failed.
Exception while firing request to remote systemNot applicable.Enable logs and contact Pega Support.
Exception while getting connection from connection poolThe system failed to get the connection to fire the request.Check logs for connection pools statistics and increase the connection pool size if necessary.
Could not get token from remote systemThe token that the security settings return is empty.Enable logs and contact your security team. Ensure that endpoints in the remote system run correctly.
Exception while getting access tokenSecurity module returns an exception.Enable logs, contact your security team and Pega Support.
Exception while renewing access tokenSecurity module returns an exception on renewing access token.Ensure that the client ID and client secret that you use to create remote case types are correct. Ensure that the endpoint in the remote system is reachable. If the client ID, client secret, and the endpoint work correctly, contact Pega Support.
Error while building socket factory for request systemThe remotesystemid element has an invalid configuration.Ensure that the configurations for tenant, keystore, and truststore are correct. If the configurations are correct, contact Pega Support.
Authorization has failed at remote systemThe remote or producer system gave a 401 response.Ensure that the client ID and client secret that you use to create remote case types are correct. Ensure that the endpoint in the remote system is reachable. If the client ID, client secret, and the endpoint work correctly, contact Pega Support.
Exception while reading post data from requestAn error with post data from the request occurred.Verify the post that the request contains. If the data is correct, contact Pega Support.
Exception while parsing request content typeThe request includes unsupported character encoding, or an exception occurred when parsing post data in the incoming request.Verify the incoming request for unsupported character encoding. If the request does not include unsupported character encoding, contact Pega Support.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us