Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

...

Expand
titleServer authentication failed


StepPossible reason(s)Possible solution(s)
1Server certificate is not available in the Truststore

Import the server certificate for outbound https connections.

You can import the certificate in either of the two,

  • Adeptia’s default Truststore (Server Kernel > etc > truststore > cacerts)
  • A custom Truststore (Develop > Services > Web Service > Security Policy > SSL Properties) you may have configured.



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
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
titleCannot activate an Event or Transaction


StepPossible reason(s)Possible solution(s)Remarks
1
  • Kernel may not be running
  • Scheduler may be paused


Visit the System Console to check,

    1. If Kernel is running.
    2. That the Scheduler is not paused.
If not solved, follow step 2.
2

Database connectivity issues

Check for the database network outages.

    1. Check the application logs for any database connectivity errors.
    2. Check with Database Admin for any network outages.
If not solved, follow step 3.
3

Event may not be associated with an Event Registry

Ensure that the Event is associated with an event registry.

If not solved, follow step 4.
4

Event may already be activated

Check if the event is not already activated.

If not solved, contact Adeptia support.


...

Expand
titleCannot activate an File/FTP Event


StepPossible reason(s)Possible solution(s)Remarks
1

Base location specified points may not be located at a valid location

Make sure that the location of base location specified points is valid.

If not solved, follow step 2.
2File location may not be accessible, or you may not have required permissions on the fileCheck if the file location is accessible and you have required permission on the file.If not solved, follow step 3.
3Base location folder may have too many files in itMake sure that the base location folder doesn't have too many files in it.If not solved, follow step 4.
4File include/exclude criteria may be the samemake sure that the file include/exclude criteria are not the same.If not solved, contact Adeptia support.



Expand
titlecannot Cannot activate Database Event


StepPossible reason(s)Possible solution(s)Remarks
1

Database server may not be accessible

Make sure that the database server is accessible using any other DB client like DBVisualizer.

If not solved, follow step 2.
2There may be client issues

Check the Application Logs for any client errors.

If not solved, follow step 3.
3There may be server related issues

Contact the Database Administrator for any server related errors.

If not solved, contact Adeptia support.


...

Expand
titleFile/FTP Event doesn't pick up the file


StepPossible reason(s)Possible solution(s)Remarks
1File location may not be accessible, or you may not have required permissions on the file

Make sure that that file location is accessible and you have have the required permissions on the file.

If not solved, follow step 2.
2File stable time may not be set to a desired value

Try increasing file stable time to a higher value.

If not solved, follow step 3.
3File may have already been processedCheck event metadata to know if the file has already been processed.If not solved, contact Adeptia support.


...

Expand
titleEvent got deactivated on its own


StepPossible reason(s)Possible solution(s)Remarks
1

Event may have reached its expiry time

Check the expiry time set for the Event.


If not solved, follow step 2.
2Event may have failed multiple times consequently and the retry count may have exceeded the count set in abpm.event.abort.retryCount propertyThe event deactivates itself when it fails multiple times consequently and the retry count exceeds the count set in abpm.event.abort.retryCount property. For more details, you can also check the Event logs for failed executions.If not solved, follow step 3.
3Starttime and endtime may be smaller than Polling Frequency.Make sure that the difference between starttime and endtime is greater than Polling Frequency.If not solved, contact Adeptia support.


...