Our general approach has been that if a user has both JRE 5 and 6 installed, s/he would only be concerned about updating the latest version (JRE 6) and not the older version (JRE 5). It is not recommended to attempt to use incomplete or corrupt install media, as critical files or components may not install or operate correctly.Your assessment is correct. If your installation media does not match the file size listed on our Support homepage, or if you suspect that the file is incomplete, you will need to re-download the ISO file. The symptoms of incomplete or corrupted install media can vary based on which files are present and missing, though this particular error has been seen alongside a message in the install.log file stating "Error: no known VMs.
This message may also appear if your installation media has become corrupt or did not download completely. Disabling security software (and possibly restarting the server if necessary) should permit normal access to all files needed for the installation. In this scenario, the installer will attempt to run setupmdb anyway, and will fail with the message "Error: Java JRE must be version 1.5 or higher".
If a security program prevents access to the file jvm.cfg, normally located at C:\Users\\AppData\Local\Temp\2\casm\mdb\jre\lib\i386\jvm.cfg, the installer will be unable to load the proper Java JRE files. The most common cause for this message is overeager security software - it is recommended to temporarily disable any security, antivirus, or antimalware programs that are present on the server prior to installation, including any run-time scanning tools. Certain security, antivirus, and antimalware programs are very aggressive in their scanning, and may temporarily or permanently block access to files that they deem 'unsafe' or 'questionable'.
0 kommentar(er)
