Error: "Bad installation. No JRE found in configuration file" when starting OM Admin Client after Update
  • KB ID: KB-01045
  • Created: 04/25/2018 7:59 AM
  • Updated: 04/25/2018 7:59 AM
  • Views: 2052
  • 0 Ratings

Symptoms

After you have been updating OperationsManager to 4.7 or changing JRE to 64 bit you might get the following error:

Bad installation. No JRE found in configuration file

Cause

This is due to the java deployment.properties has still old values (e.g. platform) after the update

Resolution

Method 1: (recommended)

  • Delete the Java folder in the users AppData\LocalLow\Sun folder (default: c:\users\<username>\AppData\LocalLow\Sun\Java)

Method 2:

  1. Open the file deployment.properties in the path explained above
  2. Edit the file and change the marked lines/values
    deployment.javaws.jre.0.registered=false
    deployment.javaws.jre.0.enabled=true
    deployment.javaws.jre.0.osarch=amd64
    deployment.javaws.jre.0.osname=Windows
    deployment.javaws.jre.0.path=C:\\Program Files\\Java\\jre6\\bin\\javaw.exe
    deployment.javaws.jre.0.location=http://java.sun.com/products/autodl/j2se
    deployment.javaws.jre.0.product=1.6.0_45
    deployment.javaws.jre.0.platform=1.6

     

More Information

Write more info here...

Products

C7, LCM6, OM4, ESI

Feedback

Did you find this article helpful?

© 2000-2018 Brainware Consulting & Development AG     Impressum / Legal Notice  |  Datenschutz / Privacy Policy