Change Resource Account Credentials

Note: See Prerequisites for Debugging Exceptions. This topic provides information about the settings to update when authenticated user credentials are changed.

Settings to connect to the Enterprise Console:

• Change Database User Settings for Windows Authentication

• Change SQL User Credentials for SQL Authentication

Settings to connect to the Central Configuration:

• Change Password of SQL User Credentials used to Connect to Repository Data Source

Reset Service Authentication

• If AVEVA Work Tasks service authentication is changed, follow the steps in Change Resource Account Credentials.

Change Database User Settings for Windows Authentication

1. On the Windows Start menu, point to Programs > AVEVA, and then click Farm Configuration Wizard.

2. The Welcome to the AVEVA Work Tasks Farm Configuration Wizard appears. Click Next.

3. The Edit AVEVA Work Tasks Farm Settings screen appears. Select Database User Settings, and then Click Next.

4. The Database User Settings screen is displayed.

   • Enter the updated User Name, Password and Domain.

   • Click OK. A message appears to confirm that the login has the required permissions.

   • Click OK. A message appears confirming that the Database User settings were successfully updated.

Change SQL User Credentials for SQL Authentication

5. On the Windows Start menu, point to Programs > AVEVA, and then click Farm Configuration Wizard.

6. The Welcome to the AVEVA Work Tasks Configuration Wizard appears. Click Next.

7. The Edit AVEVA Work Tasks Farm Settings screen appears. Click Database Settings.

8. The Connect to existing database screen appears.

   • From the Connection String option, modify the User ID and Password for connecting to the database.

   • Click Test Connection.

   • Click OK, and then Next. The user credentials are updated.

Change Password of SQL User Credentials used to connect to Repository Data Source

9. On the Windows Start menu, point to Programs > AVEVA, and then click Central Configuration.

10. The Central Configuration page appears.

11. Click Datasource Settings. The Datasource List appears.

12. In the Datasource column, click the data source you want to modify. The Manage Datasource page appears.

13. In the Connection String option, modify the User ID and Password.

14. Click OK. The password for the SQL user credentials is updated.

Change a Web Service Authentication User

15. From the selected AVEVA Work Tasks Repository, enter the Login Name and Password.

16. Click Authenticate. After successful authentication, the screen to Re-Authenticate users appears.

    • You can re-authenticate with a different user credentials if the currently authenticated user does not have the required permissions.

    • You can select, create, or edit an impersonation user from the Select User drop-down list, or use the Create New User or Edit User option.

Add an Impersonation User

17. Click Create New User. The New User screen appears.

18. Enter Display Name, Login Name and Password.

    • Provide a Windows-authenticated login name and password.

    • The login name must be preceded by the domain name.

19. Click Save.

Edit the Impersonation User

You can also create or modify an impersonation user using the Enterprise Console.

20. On the Windows Start menu, point to Programs > AVEVA, and then click Central Configuration.

21. The Central Configuration page appears.

22. Click Repository Settings. The Repository List page appears.

23. In the Site Path column, click the required repository.

24. Log on to the Enterprise Console.

25. In the Enterprise Console menu, point to Settings, and then click Impersonation User.

26. To create a new user, click New. The New User screen appears.

    • To edit an existing user select the required user and click Edit, or select Edit User from the context menu.

27. Enter the Display Name, Account Name, and Password.

28. Click Save. A confirmation message appears indicating that the impersonation user was saved successfully.

Important:
- If the password is modified in Active Directory, you must also update it in the Enterprise Console. Otherwise, workflows will fail.
- The changes take effect in the Workflow Engine only after approximately three minutes.
- Repeat these steps for all repositories where the impersonation user is used.
- Reset IIS to clear the cache.