Issues running Work Tasks

If you suspect there might be issues with Work Tasks, try the following checks and fixes.

• Make sure you are using the host's fully qualified domain name in the URLs of the web application you are trying to open:

  • Central Configuration

  • Enterprise Console

  • AVEVA Identity Manager (AIM)

  • MES Web Portal

• In the post-install Configurator, make sure that the host's fully qualified domain name has been entered on the AVEVA Identity Manager tabs of the MES DB/MW Communications and Web Portal component settings. See Configure the MES components.

• Make sure that Central Configuration and Enterprise console are using the same port number. You can use the Farm Configuration wizard to check them. See Configure the Work Tasks Farm and Enterprise Console site settings.

• Make sure all users are using their Active Directory user account to log in to the web applications.

• Check that the Work Tasks services are running and that there is connectivity with the System Management Server using the diagnostics described below.

Check Work Tasks Services and System Management Server Connectivity

In Central Configuration, run the Service Communications and System Management Server diagnostic tests. These test will indicate whether the appropriate services are running and that there is connectivity to the System Management Server, and so AIM and its token is available for use.

1. On the Central Configuration main page, click the Diagnostic Settings link.

2. Select the Service Communications and System Management Server test options, then click Test.

   

3. When the test are complete, check that they all passed, as indicated by the status messages shown in the following screen shot.

   

• If any of the required Work Tasks services aren't running, they will be listed.

  Restart the stopped services.

• If there is no connection to the System Management server, then the log will include a message indicating that a connection to the System Management Server could not be established.

  Make sure that the System Management Server is running and that there is connectivity with the node on which it is running.

• If the AIM token access failed, then the log will include a message that fetching access tokens failed.

  • Make sure that the AIM Identity Manager is running and that you can log in to it (see AIM Synchronization Issues).

  • Make sure that the AIM token is properly registered in Central Configuration.

  • In Central Configuration, make sure that the AIM token has been selected in the repository settings for the MES model-driven application content repository.