Introduction
...
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
...
Upgrading to 4.12.4.1108 from 4.12.3.1105 (MongoDb V7.0)
Database Upgrade
This version has no new features and is intended only to upgrade the database version from V6.0 to V7.0.
Note |
---|
Please be aware of the following restrictions when upgrading to this release:
|
Upgrading to 4.12.3.1105 from 4.12.2.1101 (MongoDb V6.0)
Database Upgrade
This version has no new features and is intended only to upgrade the database version from V5.0 to V6.0.
Note |
---|
Please be aware of the following restrictions when upgrading to this release:
|
Upgrading to 4.12.2.1101 from 4.12.1.1099
...
(MongoDb V5.0)
Database Upgrade
This version has no new features and is intended only to upgrade the database version from V4.4 to V5.0.
Note |
---|
Please be aware of the following restrictions when upgrading to this release:
|
Starting an Installation at Least Once
To ensure an installation has been started at least once you must:
Ensure all databases have been upgraded with the version you are trying to run.
Ensure at least one of the Management Servers has been upgraded, however if you choose to only update one you should leave the other server deactivated.
Ensure all database servers are running.
Ensure the UI application is upgraded.
Start one or more Management Servers and ensure it starts correctly.
Verify that the system has started correctly by logging in through the client UI.
Optionally you can also check the Management Server logs to ensure the upgrade did not generate any errors.
Assuming everything has started correctly and the log showed no errors, you can stop all services and upgrade to the next version.
Upgrading to 4.12.1.1099 (Mongo V4.4)
Prerequisites
This release includes version 4.4 of the MongoDb database server. This version requires the Visual Studio C++ 2019 x64 redistributable library. Technically this has been part of the Witness pre-requisites since the release of 4.11, however we recommend this is checked before installing Build 1099. Please see Software Prerequisites for more information.
...
This version fixed a bug in the licensing system and therefore requires a new licence file. Only Navtech can create a licence so you should request a new file through Customer Support.
Distance Travelled
Due to the improvement of the distance travelled settings in the rules, the travelled distance setting is now always positive. Prior to this update the distance was negative (-ve) to indicate a reverse distance and positive (+ve) for a forward direction. With the improvement, the value will now always be positive (+ve). So if you previously had a negative value this must be updated to the positive equivalent.
Note |
---|
Editing CarriagewayIf you do not update the distance travelled setting and it remain negative (-ve) you will not be able to edit and save changes to the carriageway. The value must be changed to a valid positive distance before the carriageway can be saved. |
...