Documentation for Axxon One 3.0 version. Documentation for Axxon One 2.0 version is also available.


You can update to Axxon One 3.0 only from the latest official release of Axxon One 2.0. You cannot update directly from previous releases of Axxon One (2.0.2, 2.0.4, 2.0.6, and others) to version 3.0. Example of the correct update path is 2.0 → 2.0.14 → 3.0.

After you update from the latest version of Axxon One 2.0 to Axxon One 3.0, the previously configured auto-logon function can require reconfiguration due to a change in the procedure of saving credentials.

When you update from Axxon One 2.0 to Axxon One 3.0, video may not be displayed in the web client. To restore the display of video, clear the browser cache by pressing Ctrl + F5Alternatively, you can clear the PWA cache manually through the browser's DevTools:

  1. Open the web client in the browser.
  2. Press F12 (or press Ctrl + Shift + I) to open DevTools.
  3. Go to the Application tab.
  4. Select the Storage section.
  5. Click the Clear site data button.

Before you start the update, we highly recommend you:

To update:

  1. Run the new build installer. You do not need to remove the previous build.

  2. Run the installation using the previous settings, existing configuration, and database. The procedure is the same as for a new installation (see Installation).


    Attention!

    • There are no restrictions on database location in Axxon One. To reduce the load on the system disk, we recommend storing the metadata database and the log database on a separate hard disk.
    • When you update Axxon One, only the basic DetectorPack is updated. If you installed the DetectorPack add-ons, you must update them to the version of the basic DetectorPack (see Installing DetectorPack add-ons).
    • After you update the Drivers Pack, an error can occur: “The current version of the installed Drivers Pack does not match the device configuration. The device cannot work properly until it is removed and re-added to the hardware tree.” To fix this error, you must remove the device and re-add it to the configuration. To save the rules (see Types of permissions to access hardware, archives and macros), we recommend adding devices with the original identifier (ID, see Camera) and only after that binding them to the archive (see Configuring recording to an archive).