-
Title
Receive "Auto update" dialog box switching between two databases -
Description
Receiving an "Auto update" dialog box when switching (starting a new connection) between two databases, e.g., development and production environments, when logging into front-ends such as Manager or Designer:
The dialog box says, "There are updates for your application in this database. Do you want to install them?"
This makes it unmanageable to work between the two environments (databases) when performing changes. How can this be resolved? -
Cause
Possibly by inconsistencies with some files (e.g., .dll) between the two database instances. -
Resolution
The configuration parameter, Common\Autoupdate, specifies whether automatic software updating should take place. If this configuration parameter is set, software is updated that does not have the required revision status. If the configuration parameter is not set, no automatic updating takes place.
To resolve the issue allow the updater to continue.
Technical details:
In every local installation folder there is a (hidden) file, “SoftwareRevision.viv”.
Example content:
# Do not change this file!
2130649|2013-09-09 17:14:06
This file contains a semaphore which represents the revision state. In the database (table DialogSemaphor) there is such a semaphore as well. Every time a program is started (also while the program is running) it compares the local semaphore with the value in the database. If both are different the program starts a comparison of ALL files which are contained in the local folder with the files in the database (table "DialogSoftwareRevision"). All files which are different will be replaced. In the end the “SoftwareRevision.viv” will be updated with the semaphore coming from the database.
What happens if a hotfix is installed?
If a file has been uploaded with the Software Loader into the database, it will be saved in the table "DialogSoftwareRevision". Following that, the semaphore in the database will be recalculated - then has a different (new) value. After that all programs (front-ends, Jobservice, web applications) will use the above calculation to replace the changed file. This is when the auto update runs.