PAS Error Messages

If you encounter an error not listed in this section, access the Paymetric Service Portal, and do the following:

  1. Search the Knowledge Base (KB) for a related error.

  2. If you are unable to find the appropriate information in the KB, submit a Support Request ticket.

Note: Default Trace Log Locations

  • Linux: /var/log/message.

  • Windows: Text file in the PAS install location that is named after both the executable and the process Id of the process that had the error. For example, if process Id 3420 of XiSecureNetRFC wrote to the trace file the resulting file would be named “XiSecureNetRFC.exe_3420_log.txt”.

Connectivity

Connectivity error messages include the following.

Where message displays

Validation Output (The error message output by the validation program in the PAS configuration GUI this can be seen by hovering over red/failed program after validation fails. (Starting with PAS 2.6 the error message may be copied to the clipboard.)

Possible causes

Possible invalid Client certificate, or invalid Client Certificate/Private Key certificate combination.

Corrective actions

First check that the path to the certificate and that the user used to run the PAS service has permission to read the certificate. If the path and permission are valid then check that the certificate is a valid X.509 certificate by using a tool unrelated to PAS such as “openssl” or “XCA”. If the problem persists then contact support.

Where message displays

Trace Log, EventLog

Possible causes

The program was unable to connect to the XiSecure Web Service specified in the URL or was unable to understand the response. This is often followed by another failure notice containing further information.

Corrective actions

Check that the URL is correct.

Where message displays

Trace Log, EventLog

Possible causes

The file specified by the “Gateway Host” field is not reachable.

Corrective actions

Make sure that the gateway host is a valid and reachable SAP gateway.

Where message displays

TraceLog, EventLog

Possible causes

The RFC Information field will contain a description of the error condition.

Corrective actions

RFC_FAILURE for function RfcWaitForRequest often indicates a problem with registering a particular program. Ensure that the PAS configuration panel contains identical RFC destination configuration for the specified SAP server/gateway, found in SAP SM59.

Where message displays

TraceLog, EventLog

Possible causes

Error is indicative of a communication failure between PAS server and the configured Web Service endpoint URL's.

Incorrect routing criteria (most commonly Merchant ID) is sent in the SAP packet.

Corrective actions

Ensure Internet connectivity is present on the PAS server, and that the configured Web Services URL's are reachable as well.

Ensure the correct Merchant ID (or applicable criteria) is defined in SAP. This routing value is defined in SAP and must match the routing value defined in the XiPay Server ID in the Paymetric SaaS Environment.

Where message displays

TraceLog, EventLog

Possible causes

The file specified by the “CA Certificate” field is not valid.

Corrective actions

Make sure that the file specified by the “CA Certificate” field contains a certificate chain to a trusted CA. For on demand XiSecure servers use the included gd_bundle.crt file. gd_bundle.crt is the CA installed by PAS by default, and resides in the PAS home directory.

Where message displays

TraceLog, EventLog

Possible causes

The host specified in the URL is either not trusted, or the SSL data returned is not valid.

Corrective actions

Make sure that the file specified by the “CA Certificate” field contains a certificate chain to a trusted CA. For on demand XiSecure servers use the included gd_bundle.crt file. gd_bundle.crt is the CA installed by PAS by default, and resides in the PAS home directory.

Where message displays

TraceLog, EventLog

Possible causes

WSA Account authentication failure.

Corrective actions

Verify the XiPay Web Service authentication information in the PAS configuration panel is correct.

Where message displays

TraceLog, EventLog

Possible causes

The XiSecure program was able to connect to the host specified in the URL, but the request failed according to the HTTP status code given.

Corrective actions

Check that the XiPay Web Service URL is correct in the PAS configuration panel is correct.

Authorization

Authorization error messages include the following.

Where message displays

TraceLog, EventLog

Possible causes

The RFC Information field will contain a description of the error condition.

Corrective actions

Indicates a problem with the data being passed from SAP. Validate data sent from SAP is in correct format. Contact Support for assistance in narrowing down possible data problems.

Where message displays

TraceLog, EventLog

Possible causes

The RFC Information field will contain a description of the error condition.

Corrective actions

Indicates a problem with the data being passed to SAP. Validate data sent to SAP is in correct format. Contact Support for assistance in narrowing down possible data problems.

Corrective actions

Where message displays

TraceLog, EventLog

Possible causes

PAS encountered and error trying to call XiSecure Web Service. The error should be described in the Type and Caught fields in the error message.

Corrective actions

Verify that the XiSecure endpoint URL is valid and that it's confirmed as functional.

Reconciliation

Reconciliation error messages include the following.

Where message displays

TraceLog, EventLog

Possible causes

The RFC Information field will contain a description of the error condition.

Corrective actions

Indicates a problem with the data being passed from SAP. Validate data sent from SAP is in correct format. Contact Support for assistance in narrowing down possible data problems.

Where message displays

TraceLog, EventLog

Possible causes

The RFC Information field will contain a description of the error condition.

Corrective actions

Indicates a problem with the data being passed to SAP. Validate data sent to SAP is in correct format. Contact Support for assistance in narrowing down possible data problems.

Where message displays

TraceLog, EventLog

Possible causes

PAS encountered and error trying to call XiSecure Web Service. The error should be described in the Type and Caught fields in the error message.

Corrective actions

Verify that the XiSecure endpoint URL is valid and that it's confirmed as functional.

Settlement

Settlement error messages include the following.

Where message displays

TraceLog, EventLog

Possible causes

The RFC Information field will contain a description of the error condition.

Corrective actions

Indicates a problem with the data being passed from SAP. Validate data sent from SAP is in correct format. Contact Support for assistance in narrowing down possible data problems.

Where message displays

TraceLog, EventLog

Possible causes

The RFC Information field will contain a description of the error condition.

Corrective actions

Indicates a problem with the data being passed to SAP. Validate data sent to SAP is in correct format. Contact Support for assistance in narrowing down possible data problems.

Where message displays

TraceLog, EventLog

Possible causes

PAS encountered and error trying to call XiSecure Web Service. The error should be described in the Type and Caught fields in the error message.

Corrective actions

Verify that the XiSecure endpoint URL is valid and that it's confirmed as functional

Tokenization

Tokenization error messages include the following.

Where message displays

TraceLog, EventLog

Possible causes

The RFC Information field will contain a description of the error condition.

Corrective actions

Verify that the XiSecure endpoint URL is valid and that it's confirmed as functional.

Where message displays

TraceLog, EventLog

Possible causes

The RFC Information field will contain a description of the error condition.

Corrective actions

Verify that the XiSecure endpoint URL is valid and that it's confirmed as functional.

Where message displays

TraceLog, EventLog

Possible causes

The RFC Information field will contain a description of the error condition.

Corrective actions

Verify that the XiSecure endpoint URL is valid and that it's confirmed as functional.

Where message displays

TraceLog, EventLog

Possible causes

Error occured calling XiSecure Web Service.See FaultDetail field in error message.

Corrective actions

Verify that the XiSecure endpoint URL is valid and that it's confirmed as functional.

Where message displays

TraceLog, EventLog

Possible causes

Error occured calling XiSecure Web Service.See FaultDetail field in error message.

Corrective actions

Verify that the XiSecure endpoint URL is valid and that it's confirmed as functional.

Where message displays

TraceLog, EventLog

Possible causes

Error occured calling XiSecure Web Service.See FaultDetail field in error message.

Corrective actions

Verify that the XiSecure endpoint URL is valid and that it's confirmed as functional.

Where message displays

TraceLog, EventLog

Possible causes

Error occured calling XiSecure Web Service.See FaultDetail field in error message.

Corrective actions

Verify that the XiSecure endpoint URL is valid and that it's confirmed as functional.