Diagnostics

The Diagnostics feature allows you to run the diagnostics tests and determine if AVEVA Work Tasks is functioning properly. You can also configure the request limitations for uploading attachments in AVEVA Drive storage.

You can select the services and run the diagnostics test to know the status of the selected services. The status of the selected services is displayed in the Logs section of the Diagnostics page. You can also filter the logs based on Pass or Fail status of the services, export the Logs, and maximize the Logs view.

Configure Request limits

You can set the request limitations for the application. These settings would help in addressing the limits for uploading attachments in Database or AVEVA Drive storage. Below are the parameters, which you can set:

• Timeout: Set the timeout in seconds, after which the system logs the timeout message for exceeding the time set for a request. The default value is 900 seconds and the minimum value is 10 seconds. The timeout should be between 10 and 9999 seconds. This setting would also apply when you upload an attachment.

• Content Limit: Set the size for the content set in a request. The maximum allowed size is 500 MB. The default value is 30 MB. This setting would also apply to an attachment size to be uploaded. The Content-Length should be between 10 and 500 MB. The recommended value for content limit is 30 MB.

Configure Log levels

You can select the Log levels to display the relevant messages. The following Log levels are available:

Level 1: This level shows minimal information in the Logs section. The Logs section displays information related to the start and end of a workflow. Error messages are also shown in this mode.

Level 2: This level provides detailed information of background activities. It will show all the messages logged from the actions.

Level 3: This level displays messages indicating whether an action is executed.

Run Diagnostics test

The following services can be diagnosed to check their availability in AVEVA Work Tasks:

• Azure Service Bus Relay: Tests whether Azure Service Bus Relay is configured and the response is received from Http Web Request.

• Message Broker (amqp/amqps): Tests whether the repository is provisioned and the Message Broker (amqp/amqps) exist in the repository.

• Mobile Notification Service: Tests whether Mobile Notification Service is running.

• Quickflow: Tests whether Quickflow is deployed, AMQP protocol is validated on the Message Broker, and Quickflow Host is connected.

• Service Communication: Tests whether Enterprise Server service and all the AVEVA Work Tasks services are running.

To run the Diagnostics test:

1. Access the Central Configuration URL (for example, https://worktasks.connect.aveva.com/CC123456789).

   The Central Configuration page appears.

2. Click Diagnostics Settings.

   The Diagnostics page appears.

3. Select the check box against the items for which you want to run the diagnostics tests and then click Test button.

   After the diagnostic test is complete, the status of the selected items appears in the Logs section of the Diagnostics page.

Reset IIS

After you change the log level, click the Reset IIS button in the Diagnostics page to reset IIS and update the log level. On IIS reset all the AVEVA Work Tasks sites will get restarted.

Restart all services

After you change the log level, click Restart Service button in the Diagnostics page to restart all the AVEVA Work Tasks services and update the log level.

Note:
- If you modify the log level, ensure to restart services and reset IIS to update the log level.
- IIS reset and service restart takes time and should not be initiated simultaneously.
- When the Timeout and Content Limit values are updated and saved, or when an IIS reset is performed, all active Enterprise Console sessions are terminated, and users must log in again.
- Default session timeout is 40 minutes. If your session expires due to inactivity, you will see a message stating: Your session has expired. Please close the browser and log in again.
To continue using the Enterprise Console, click Login and re-enter your credentials.