Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Using Java Plug-in 1.6.0 Update 10 (1.6.0_10) or newer with Version Manager releases prior to VM 8.2 can corrupt your project database
P2470 , or upgrade to VM 8.2 or newer. Users of older VM releases should cease using all versions of the Java 1.6 Plug-in to avoid (further) database corruption, and upgrade their Version Manager release to VM 8 .2 as soon as possible.
CMS-XML Web Client throws missing JRE error on Linux when using Java 7 Update 71 and newer or Java 8 Update 20 and newer
yum install gtk2-engines gtk2-devel If you use the i686 versions of the browser (e.g. firefox.i686) and the JRE on an x86_64 version of Linux, run the following command instead:
CMS-XML VM I-Net Web Client no longer works from Firefox after upgrading to Java 8 Update 91 (1.8.0_91)
In Chrome, first check if you are running Chrome Version 42 or newer. If you are, see KB doc S141138 .
CMS-XML VM 8.5.3 Patch 003: HotFix for VM 8.5.3 to solve issue using Web Client with Java 8 Update 91 from Firefox
If you access the VM I-Net Web Client via an older version of Internet Explorer, please see KB doc D23489 after installing this HotFix.
CMS-XML VM: Error: "You must install a Solaris patch to run this version of the Java runtime. Please see the README and release notes for more information. Exiting." when some users launch VM using SETUID mode on Solaris.
On Solaris 8 , create the symbolic links in the directory: /usr/lib/secure If you are using a version of Solaris older than 8, use the following command to determine which directory to create the links in:
CMS-XML VM I-Net 8.4.x never shows OK button on login screen and/or shows error message "java.lang.RuntimeException: java.lang.ExceptionInInitializerError" when using Java 7 (1.7.0)
PVCS Version Manager 8 .4
CMS-XML VM I-Net: Java 7 Update 21 and Java 6 Update 45 trigger warnings for the Java version check applet
A HotFix addressing this and other issues is available for VM 8 .4.6. This patch can be downloaded from KB article
CMS-XML 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
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.
CMS-XML VM 8.2 - 8.4.3: Desktop Client GUI fails to launch. Console mode shows Exception in thread "main" java.lang.ExceptionInInitializerError
To avoid this problem, either use a VM Desktop Client release that is not affected by this problem (8.4.4 or newer), or avoid redefining the Java system property java.vendor. Typically this is done as a hack, to make a Java application work with a Java release that it was not designed for, and the better solution is to find an updated version of that application.
CMS-XML Hotfix for Version Manager
ENH208985: Ability to access item page in VM I-Net via hyperlink containing Japanese chars DEF209984: VM I-Net users sent to login page on module association with Java plugin 1.6.0_29 DEF206112: VM webclient is not working with JRE 7 (1.7.0)
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs