Make sure all directories and folders are closed during the upgrade process.
If performing an in-place upgrade, open the config/agiliance.properties file and comment out the com.agiliance.esapi.allowed.file.extensions property. To comment it out, place a # character at the beginning of the line where the property exists and save it. After the upgrade is complete, you can uncomment the property.
RiskVision does not support Internet Explorer version 8 or Internet Explorer Compatibility mode, which causes the browser to run like it was a version 8 browser.
If you are on RiskVision 7.5, 8.0, and 8.5x or 9.0 versions, you can directly upgrade to RiskVision 9.2. From there, users can upgrade to 9.3.
To use MySQL, you must install Visual C ++ 2015 - 2022 Redistributable (x64) - 14.32.31332 before upgrading/installing RiskVision 9.7.1.
The below table shows the recommended upgrade paths depending on the current version of RiskVision:
9.7.1
-
FROM VERSION | TO VERSION |
7.5 | 9.1 or 9.2 (recommended) |
8.0 | 9.1 or 9.2 (recommended) |
8.5 (all variations) | 9.1 or 9.2 (recommended) |
9.0 | 9.1 or 9.2 (recommended) |
9.1 | 9.2 or 9.3 |
9.2 | 9.3 or 9.3.5 |
9.3 | 9.3.5 or 9.4 |
9.3.5 | 9.4 or 9.5 |
9.4 | 9.5 and 9.6 |
9.5 | 9.6 and 9.7 |
9.6 | 9.7 and 9.7.1 |
9.7 | 9.7.1 |
9.7.1 | - |
Important: If upgrading from the 7.5 release, verify in the agiliance.properties file that the jasper.use.secure.connection=FALSE property is not set. If it is, delete the property from the agiliance.properties file.
For more information on the UAC setting, see Configure the UAC Setting.
