Troubleshooting events and web services

1

There may be connectivity issues.

1. Check the connection by opening any web page on the browser.

2. Check the Proxy configuration.

3. Contact your Network administrator to allow non-browser inbound or outbound calls.

Follow the steps in same sequence as provided in the Possible solution(s) column.

1

Server 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.

1

Improper/Incorrect configuration of client Keystore

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

1

Timeout settings are not set as required

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

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.

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.

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.

1

The SSL certificate may have expired

Update the SSL certificate.

1

Either Keystore file is corrupt, or password supplied for Keystore is incorrect

Contact your Administrator for correct password of this Keystore.

1

Either Keystore file is corrupt, or password supplied for Keystore is incorrect

Contact your Administrator for correct password of this Keystore.

1

A 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.

1

The client has sent the expired or invalid certificate to server

Make sure that the client certificate valid.

1

• Kernel may not be running

• Scheduler may be paused

Visit the System Console to check,

1.  

   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.  

   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.

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.

2

File location may not be accessible, or you may not have required permissions on the file

Check if the file location is accessible and you have required permission on the file.

If not solved, follow step 3.

3

Base location folder may have too many files in it

Make sure that the base location folder doesn't have too many files in it.

If not solved, follow step 4.

4

File include/exclude criteria may be the same

make sure that the file include/exclude criteria are not the same.

If not solved, contact Adeptia support.

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.

2

There may be client issues

Check the Application Logs for any client errors.

If not solved, follow step 3.

3

There may be server related issues

Contact the Database Administrator for any server related errors.

If not solved, contact Adeptia support.

1

Scheduler may not be running

Check the System Console for Scheduler status. It should be in running state.

If not solved, follow step 2.

2

Job interruption may have occurred

Check the Application Logs for any error related to Job interruption. This interruption error is temporary. Try to deactivate the transaction again after some time.

If not solved, contact Adeptia support.

1

Scheduler may not be running

Check the System Console for Scheduler status. It should be in running state.

If not solved, follow step 2.

2

Job interruption may have occurred

Check the Application Logs for any error related to Job interruption. This interruption error is temporary. Try to deactivate the transaction again after some time.

If not solved, contact Adeptia support.

1

File 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.

2

File 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.

3

File may have already been processed

Check event metadata to know if the file has already been processed.

If not solved, contact Adeptia support.

1

Event may have reached its expiry time

Check the expiry time set for the Event.

If not solved, follow step 2.

2

Event may have failed multiple times consequently and the retry count may have exceeded the count set in abpm.event.abort.retryCount property

The 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.

3

Starttime 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.

1

The expiry date set for the event may be invalid.

Set a valid expiry date.

If you don't want the event to be expired, don't specify the expiry date and time.

1

 Database query may have been specified without a schema name.

Add schema name with table name while writing query in DB Event. Ex. SELECT * from SYSTEM.Person where firstName="john".

1

The event may have picked up the files before deactivation and the files may still be in the queue to be processed even after the deactivation of the event.

Remove the queued execution of files from Administer > Maintenance > Queue Processor.

1

The event may have expired.

Deactivate the event, adjust the start and end time, and activate the event.

1

This issue may happen due to various reasons

Note the status code and check for App documentation for that status code.

View the application Kernel logs to find out the additional details of the error.

1

This issue may happen due to various reasons

Note the status code and check for App documentation for that status code.

View the application Kernel logs to find out the additional details of the error.

1

There may be NullPointerExceptions at the backend

Check the application logs to find out the location of the NullPointerException. Contact Adeptia support for the analysis of NullPointerException.

1

Some exception may have occurred at server while processing the request

Read the exception message to know what may have caused the exception.

To know the exact class and method from which the exception has occurred, check the application logs. The error stack trace within logs would indicate the exact class and method that may have caused the exception.