VM I-Net no longer works following the release of Java 7 Update 51 (on January 14th 2014) if an older version of the Java plug-in is installed

ID:    S140200
Published:    15 January 2014
Updated:    08 April 2015

Operating System(s)

  • All Unix
  • All Windows


  • PVCS Version Manager


Since the release of Java 7 Update 51, users of older versions of the Java plug-in (like Java 7 Update 45) get the error message:


This browser has no Java Runtime Environment (JRE).
VM web client needs JRE 1.5 or later. Please click on this link to download and install a Java Plug-in.


when attempting to access vminet.html or when trying to login to a servlet.
This is caused by logic inside all Java plug-ins released as of Java 7 Update 25 that checks if Java updates are available, and blocks a vital mechanism needed by VM I-Net (LiveConnect) if such an update was found. Quoting from
  • LiveConnect Blocked under Some Conditions

    LiveConnect calls from JavaScript to Java API are blocked when the Java Control Panel security slider is set to Very High level, or when the slider is at the default High level and the JRE has either expired or is below the security baseline.

The moment the JRE detects that a newer version is available, which it does by checking Oracle's website, it will disable LiveConnect on the older, currently installed JRE.

(This can be confirmed by looking at the Java console with tracing enabled. There you will see:
network: Created version ID:
network: Created version ID:
security: LiveConnect (JavaScript) blocked due to security settings.


where is an example of the currently installed JRE and is the newer version that the JRE found on the Internet.)
Installing the newer JRE may not be an option, as it might not be compatible with the Version Manager release you are running. For example, Java 7 Update 51 will not run with VM 8.4.x.


To be able to continue using the older JRE installation, do one of the following:
  • For sufficiently new JRE versions that have this feature, add the URL to VM I-Net server to the Exception Site List on the Security tab of the Java Control Panel.
  • Disable run-time checking of newer JRE versions. This can be done by editing the file %LocalAppData%Low\Sun\Java\Deployment\ while no JRE is running.
    You can edit this file by executing the command:
    notepad "%LocalAppData%Low\Sun\Java\Deployment\"
    or, on systems that do not have %LocalAppData% (like Windows XP or Windows 2003):
    notepad "%APPDATA%\Sun\Java\Deployment\"
    In this file, add the line:

Once in place, the currently installed JRE should continue to work as before.

Rate this Solution

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs