Configuration Database Regeneration – All Clients
In the event that a remote application is experiencing client synchronization problems, and the configuration database has become corrupted, you can command VTS to regenerate Config.db on all clients 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 configuration server.
2. Open the VAM on the configuration server.
3. Select the application.
4. Click the VAM's Properties button. The Application Properties dialog opens.
5. Select the "Force Clients to Synchronize: Files" checkbox.
6. Click the OK button. A dialog opens to caution you that all clients must be restarted to synchronize their configuration database files.
• Click the OK button. All clients will be forced to restart, thereby receiving an uncorrupted copy of the configuration database from the server.