Force One Client to Synchronize with the Primary Configuration Server
When a single client appears to have corrupted data, and is not displaying the same data as the other workstations running a remote application, you should force that client to synchronize with the primary configuration server.
You have three choices for forced synchronization of a single client:
• Force the client to synchronize its tags with that of the primary configuration server. The primary configuration server will delete the replica tag database ("SCT.mdb") on the client workstation and replace it with an uncorrupted copy.
• Force the client to synchronize its files with that of the primary configuration server. The primary configuration server will delete the configuration database ("Config.db") on the client workstation and replace it with an uncorrupted copy.
• Force the client to synchronize its 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 the client workstation 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 client, 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 client workstation.
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 synchronization of tags, files or both.
• To force synchronization of tags, click the Force Synchronization Of: Tags checkbox.
• To force synchronization of tags, click the "Force Synchronization Of: Files" checkbox.
A dialog opens warning you that all modifications made to files on this workstation will be lost if you proceed.
6. Click the "OK" button on the dialog.
7. Click the "OK" button on the "Application Properties" dialog.
If you chose to replace tags, VTS will replace the replica tag database ("SCT.mdb") with an uncorrupted copy from the server. If you chose to replace files, VTS will replace the configuration database ("Config.db") with an uncorrupted copy from the server.
8. Restart the application on the client.
• The following steps apply only if files were synchronized:
9. Logon to the remote application on the client 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. The "Remote Configuration" dialog opens.
12. Release any locks on the files held by the client (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.