Some of the problems that may occur during execution of the Skelta Workflow.NET application are covered here. These are discussed with respect to the module that they occur in, along with the probable cause and the suggested corrective action.

When Executing / Controlling Workflows

1. The engine is not running.

Causes : (i) The Skelta Workflow.NET Engine may not be running.

(ii) Attempting to run a workflow that is not deployed.

(iii) An exception is thrown when the workflow cannot be controlled.

Corrective Action : Check for the above conditions and try again.

Using Custom Actions

1. The custom actions are not working.

Causes : (i) The assembly/class name is not properly configured.

(ii) The custom action does not implement IActionRun interface.

(iii) The custom action does not handle exceptions.

Corrective Action : Check for the above conditions and try again.

Using Web Controls

1. The web controls are not working properly.

Causes : (i) The properties are not properly configured.

(ii) The Skelta Workflow.NET Engine was not running when executing the controls.

Corrective Action : Check for the above conditions and try again.

In Skelta Services

1. The service may not start.

Causes : (i) Connectivity to the database could not be established using the database configuration string.

Corrective Action : Check the database configuration string for any errors and try connecting again.

2. The service takes too long to start or takes up too much of CPU resources.

Causes : (i) The services are attempting to execute pending actions.

Corrective Action : Close any pending actions and try again.

3. The Workflow Engine may throw the exception: 'Start.gif could not be found'

Corrective Action : Check the Interact with Desktop for that service.

4. The Engine is not able to connect to the Jabber Server.

Causes : (i) Incorrect network settings.

(ii) Network security settings.

Corrective Action : Check the above conditions and try again.