Versions Compared

Old Version 43

changes.mady.by.user Guy Avery

Saved on

compared with

New Version 44

changes.mady.by.user Guy Avery

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

...

Table of Contents
maxLevel3
indent16px
excludeIntroduction|Contents

...

Upgrading to 4.12.2.###

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:

  • You can only upgrade to this version from 4.12.1.1099. Because of the database requirements all upgrades must happen in sequence.

  • You must have started the installation of 4.12.1.1099 at least once before upgrading to this version. Please see the note below on the requirements for starting a system at least once.

Starting an Installation at Least Once

To ensure an installation has been started at least once you must:

  1. Ensure all databases have been upgraded with the version you are trying to run.

  2. 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.

  3. Ensure all database servers are running.

  4. Ensure the UI application is upgraded.

  5. Start one or more Management Servers and ensure it starts correctly.

  6. Verify that the system has started correctly by logging in through the client UI.

    1. Optionally you can also check the Management Server logs to ensure the upgrade did not generate any errors.

  7. 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

Prerequisites

...

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 Carriageway

If 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.

...