When multiple clients appear to have corrupted data, and are not displaying data correctly, you should force all clients to synchronize with the primary configuration server.
You have three choices for forced synchronization of all clients:
• Force the clients to synchronize their tags with that of the primary configuration server. The primary configuration server will delete the replica tag database ("SCT.mdb") on all client workstations and replace it with an uncorrupted copy.
• Force the clients to synchronize their files with that of the primary configuration server. The primary configuration server will delete the configuration database ("Config.db") on all client workstations and replace it with an uncorrupted copy.
• Force the clients to synchronize their tags and files with that of the primary configuration server. The primary configuration server will delete both the replica tag database ("SCT.mdb"), and the configuration database ("Config.db") on all client workstations and replace them with uncorrupted copies.
Note: Performing any of the above actions will cause any modifications to resource items that have been made on the clients, but that have not yet been updated to be lost.
Steps to synchronize one client with the Primary Configuration server:
1. Open the VAM on the primary configuration server.
2. Stop the application.
3. Ensure the application is selected in the VAM's Available Applications list.
4. Click the Properties button on the VAM. The Application Properties dialog opens.
5. Decide whether to force clients to synchronize tags, files or both.
• To force synchronization of tags, click the Force Clients To Synchronize: Tags checkbox.
• To force synchronization of tags, click the Force Clients To Synchronize: Files checkbox.
A dialog opens warning you that all modifications made to tags on all workstations will be lost if you proceed.
6. Click the OK button on the dialog.
7. Click the OK button on the Application Properties dialog.
VTS will force all clients to stop their application. If tags are being synchronized it will replace the replica tag database (SCT.mdb) on each client running the application with an uncorrupted copy from the server.
8. Restart the application on the server.
• The following steps apply only if files were synchronized:
9. Logon to the remote application on the primary configuration server using a user account that has been granted all system privileges.
10. Click the Configure button. The Configuration Toolbox opens.
11. Click the Remote Configuration button.
12. Release the locks on the files held by the primary configuration server (the Locked By column should identify the name of the workstation that has the lock). (If you need instructions on releasing locks, please refer to Release a Lock).
13. Close the Remote Configuration dialog.
14. Close the Configuration Toolbox.
15. Restart the application on the clients.
The section that follows provides instructions on forcing all clients to synchronize files with the primary configuration server.