Troubleshoot Issues

1. While executing the BAPI_RFC Execute activity, the logger might log the following error message:

The parameter: RETURN cannot appear in XML message..... as shown in the following image:

Solution

• Go to BAPIRFC Execute activity and select the No option in the Include Return Parameter property.

3. The following error message appears:

An error occurred while parsing the xml. Length of variable: DOC_DATE is 0 but expected length is 8.

The Date Time type parameter must always be provided with the required values.

Solution:

You can either provide the required value to all the Date Time type parameters or delete the nodes from the Input XML Variable present in the Start activity. To delete the node, right-click the node, delete it, and save the variable.

4. Unable to send or receive emails and SMS using the AVEVA Work Tasks Communication Service.

Possible Cause

The Communication Service is hosted on Port 25. If any other application or process uses the same port, the port will be unavailable to the Communication service. Hence, you will not be able to send and receive emails and SMS.

 

Solution

After you restart the Communication Service, we recommend you to use Telnet to verify the availability of port 25. This helps you to ensure that the communication service is started and running. However, ensure to maintain a time delay of a minute between the communication service restart and Telnet.

Use the following command to verify the availability of port 25:

Telnet <Computer Name> 25

5. When upgrading a large database, the following error appears:

The transaction associated with the current connection has completed, but has not been disposed. The transaction must be disposed before the connection can be used to run SQL statements.

Possible Cause

Upgrading a large database takes more than 10 minutes, due to the size of the database, but the default transaction timeout settings is 10 minutes.

Solution

Increase the transaction timeout settings in the machine.config file as follows:

<system.transactions>

<machineSettings maxTimeout="01:00:00"/>

</system.transactions>

6. Start Activity slows down and takes time to start when the workflow is executed.

Possible Cause

The invalid web service was registered in the Repository.

Solution

Make the necessary changes in the web service URL and ensure that the web service URL is valid.

7. When trying to create Scheduler Association from the Web server/ Engine server in the Enterprise Edition environment, the following error occurs:

Error while scheduling the workflow., - Cannot open SkeltaTaskScheduler2 service on computer 'Server2'., Inner Exception: Access is denied

Solution

Create an Enterprise Console site on the server specified in the error message (e.g., Server2) and access the Enterprise Console from the same server to perform the association.