Introduction
...
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
Upgrading to 4.12.0.1099
Pre-Requisites
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.
| Info |
|---|
Although the minimum requirement is C++ 2019, the recommended redistributable library is now Visual Studio C++ 2015-2022 x64. This will provide support for the upcoming releases which will all have newer versions of the MongoDb server. |
.NET 8 Upgrade
This version is built on the latest Microsoft .NET technology stack. All necessary support files are shipped with the product so additional action is required, however be aware that .NET 8 is only supported on the following versions of Windows:
Windows 10 Build 1607 and newer.
Windows 11 Build 22000 and newer.
Windows Server 2012 and newer.
Database Authentication
Database authentication is supported in this release. If you need to implement it then please refer to Database Authentication. All configuration associated with the database authentication is done after installation.
Log Rotate
This version now automatically installs a Windows Scheduler Task to rotate the MongoDb logs every 24 hours. It is strongly recommended that any existing logs associated with older methods of log rotation are deleted before the task first runs to avoid any potential conflicts and confusion.
| Info |
|---|
Note that the Log Rotate task requires the necessary password details to access the database once authentication is enabled. This is all covered in the Database Authentication documentation. |
Upgrading to 4.12.0.1073
Code Signing Certificate
...
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. |
...