Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleClient Authentication failed


StepPossible reason(s)Possible solution(s)
1Improper/Incorrect configuration of client Keystore

Make sure you configure the client Keystore correctly.
Configuring Keystore (Develop > Services > Web Service > Security Policy > SSL Properties)

...



Expand
titleThe request does not timeout

...

, or

...

time out before completion


StepPossible reason(s)Possible solution(s)
1Timeout settings are not set as required

Check the timeout settings in Advanced Properties of Web Service activities.



Expand
titleProblem in making

...

connection with WSDL: WSDL not found.


StepPossible reason(s)Possible solution(s)
1

WSDL path is misconfigured, or WSDL doesn't exist at the set location

Check the “abpm.webservice.wsdlDeployPath” property value for WSDL Location and then go to that location if WSDL exists.

Info
In clustered environments make sure that you configure the WSDL deploy path as shared path.




Expand
titleProblem in accessing WSDL file. Could not import <name> xsd


StepPossible reason(s)Possible solution(s)
1

WSDL path is misconfigured, or WSDL doesn't exist at the set location

Make sure that you configure the file references properly for the selected WSDL.

Make sure that XSD is accessible if it is on the Web.



Expand
titlePKIX Building Failed. Unable to find valid certification path to requested target


StepPossible reason(s)Possible solution(s)
1

Server certificate may not be present in the default/configured Truststore

Check if the server certificate is present in the default/configured Truststore or not.




Expand
titlePKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed


StepPossible reason(s)Possible solution(s)
1

The SSL certificate may have expired

Update the SSL certificate.



Expand
titlejava.io.IOException: Keystore was tampered with, or password was incorrect


StepPossible reason(s)Possible solution(s)
1Either Keystore file is corrupt, or password supplied for Keystore is incorrect


Contact your Administrator for correct password of this Keystore.



Expand
titlejava.io.IOException: Keystore was tampered with, or password was incorrect


StepPossible reason(s)Possible solution(s)
1Either Keystore file is corrupt, or password supplied for Keystore is incorrect

Contact your Administrator for correct password of this Keystore.



Expand
titlejava.security.UnrecoverableKeyException: Cannot recover key


StepPossible reason(s)Possible solution(s)
1A key in the Keystore cannot be recovered when it is tried to be accessed with a wrong password

Make sure that you use the right password.




Expand
titleReceived fatal error: Bad Certificate


StepPossible reason(s)Possible solution(s)
1The client has sent the expired or invalid certificate to server

Make sure that the client certificate valid.


Events

  • I cannot activate an Event or Transaction. 
  • I cannot activate an File/FTP Event
  • I cannot activate Database Event.
  • I cannot deactivate an Event or Transaction.
  • File/FTP Event is not picking up the file.
  • My event got deactivated itself.
  • Error in activating FTP Event. Couldn't store trigger for job: data exception: numeric value out of range.
  • Where condition is not working in DB event in Oracle.
  • Event is deactivated but still files are getting processed.
  • Event is activated: Next fire time is null or Not available.
  • Error while executing <appName> event: Reason: Unable to read response data.
  • Error while executing <appName> event: Reason: The response code is not valid.
  • Error while processing request: null
  • Error while processing request: Internal Server Error : <exception message>

...