These instructions will guide you in installing the latest version of DBDOC over a previous version.
We recommend that you update the different components of DBDOC in the following order. This will ensure that no data is lost and will minimize live data downtime during the update.
To update DBDOC:
It is important to rebuild your project immediately before updating. This lets you keep the management of change descriptions generated by DBDOC accurate across the update.
This new project file will also be useful as a backup if you have any problems with the update.
ERROR_FILES
folder.
ERROR.7Z
to ERROR-old.7z
. This will differentiate your old error files from the new ones.
Note: If CIUMon is running on a computer that should not be rebooted, please contact GMCL.
Updating CIUMon first ensures that live data is available throughout the rest of the update process. Note that you will need administrator privileges to update CIUMon.
If CIUMon is running on the desktop, exit it now. If it is running as a service it will be stopped and restarted automatically when you install the new version.
The new version of CIUMon will be installed in the same location as the old version. The update method now depends on where CIUMon is installed.
Note: If you find the CIUMon is installed in BOTH of the locations below on a single computer, please contact GMCL before continuing with the update. Two CIUMon installations on a single computer may cause problems.
Note: If you are not sure how CIUMon was installed, you may try either of the following update methods. If you try the wrong method, you will get an error message indicating that you need to use the other method instead.
In this case, CIUMon was installed with the Build System, and you should now update the Build System and CIUMon together. Follow the instructions in Step 3: Updating the Build System, then come back and verify that the new version of CIUMon works.
In this case, CIUMon was installed with the CIUMon kit, and you need to update CIUMon by itself.
CIUMon_NT4_Kit.exe
.
CIUMon_W2K_Kit.exe
.
Run CIUMon manually to make sure that it will run and connect to the CIU correctly. Once it is connected, the messages in the CIUMon window will end with a green "OK".
If you run multiple CIUMon processes, verifying that each of them works is critical. Note that only the first one you run will know which configuration to use. You will have to select the correct configuration for the other CIUMon processes when you test them.
If you usually run your CIUMon processes as services, quit CIUMon once you have verified that it works so that you can restart the services.
In the Windows Services Manager, find each CIUMon service and start it.
Open Task Manager (press Ctrl+Shift+Esc). Check that the correct number of CIUMon processes are running in the "processes" display.
Now make sure that Hyperview users can access live data.
Update BuildPlus on the computer that you use to do builds. Note that you will need administrator privileges for this update.
You can also download the installers from our website.
We recommend updating Hyperview before you rebuild your project. This will ensure that the version of Hyperview you are using will be able to take advantage of any changes or improvements we have made.
Updating Hyperview next ensures that users will be able to open the new project file when you build it. There are two different procedures for updating Hyperview, depending on whether it is possible to schedule a time when no users are currently using it. It is slightly more involved to update Hyperview while it is in use, so use Option 1 if you can be certain nobody currently has Hyperview open.
Use this method if you are the only Hyperview user, or you can be sure that no other Hyperview users have it running.
Unless you use Option 2 (below), the old version of Hyperview cannot be replaced while people are using it. All users will need to stop using Hyperview briefly during the update. Select a time when few users will be using Hyperview, and notify Hyperview users about the coming update. If you have multiple Hyperview installations (for instance, on your secure LAN and on your business LAN), schedule an update time for each installation.
The new version of Hyperview must be installed as the same location as the old version, so that Hyperview users' shortcuts will continue to work. Make sure to check the locations for all your Hyperview installations.
For each shared Hyperview installation:
The new version of Hyperview must be copied to the same location as the old version, so that Hyperview users' shortcuts will continue to work.
For each shared Hyperview installation:
Programs
folder to Programs_old
and Documents
to Documents_old
.
C:\DBDOC\Hyperview
to the shared folder.
For each shared Hyperview installation:
On a computer that uses that installation, double-click the Hyperview shortcut. Hyperview should open your project.
If there are any problems with this step, please contact GMCL.
Use this method if it is difficult to ensure that there are no open copies of Hyperview running anywhere from the shared installation location. It is a little bit more involved than Option 1.
The new version of Hyperview must be installed as the same location as the old version, so that Hyperview users' shortcuts will continue to work. Make sure to check the locations for all your Hyperview installations.
For each shared Hyperview installation:
The new version of Hyperview must be copied to the same location as the old version, so that Hyperview users' shortcuts will continue to work.
For each shared Hyperview installation:
Hyperview_Kit.exe
and follow the instructions on screen to install the kit.
C:\DBDOC\Hyperview\Programs
to C:\DBDOC\HYPERVIEW\Programs_new
C:\DBDOC\HYPERVIEW\Programs_new
to the enclosing folder of the shared Programs folder. The enclosing folder will now contain Programs
(with the old hyperview.exe
), and Programs_new
(with the new hyperview.exe
).
hyperview.exe
in the shared Programs
folder to hyperview_old.exe
(there should be no problem doing this).
XpdfRasterizer.dll
in the shared Programs
folder to XpdfRasterizer_old.dll
.
Programs_new
to Programs
. Confirm replacing anything with the same name. There should be no complaints of the "file is open" variety. The new version of hyperview.exe
will now be in the shared Programs
folder.
When a user restarts the running Hyperview from their usual shortcut, the new version of Hyperview will be used.
For each shared Hyperview installation:
On a computer that uses that installation, double-click the Hyperview shortcut. Hyperview should open your project.
If there are any problems with this step, please contact GMCL.
Rebuild your project, and put the new project file file in the shared folder.
Open BuildPlus. On the Build menu, click Build.
Note: After updating from DBDOC version 10.3.1 or earlier, BuildPlus will convert your projects to our new node format. This may take several minutes. This conversion will occur only once.
If there are any errors, stop and contact GMCL.
"[Hyperview install location]\hyperview.exe" "[shared project files location]\*.dbdoc"
. The wildcard (*) tells Hyperview to open the newest project file.