In the event that a single client running a remote application is experiencing synchronization problems, and the configuration database has become corrupted, you can command VTS to regenerate Config.db on that client using the server's copy.
Note: Users familiar with versions prior to VTS 5.0 may have used a reset method of stopping the application and deleting the configuration database to resolve file corruption. This technique is strongly inadvisable. Please follow the instructions below for the appropriate method of resolving file corruption.
Before you begin, it is recommended that you first update all file and tag editing changes on all workstations prior to forcing synchronization. This will ensure that no changes are lost.
1. Stop the application on the client.
2. Open the VAM on the client.
3. Select the application.
4. Click the VAM's Properties button. The Application Properties dialog opens.
5. Select the "Force Synchronization Of: Files" checkbox.
6. Click the OK button. When this client restarts, it will receive an uncorrupted copy of the configuration file database from the server.