Find Answers

Filter Search Results
All Operating Systems:
All Products:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
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 VM: Known issues with Version Manager 8.0.2.0
2b. Users are not able to browse the local file system in the VM I-Net client using certain versions of the Sun Java plug-in.
CMS-XML Potential file corruption when File Server is used by Version Manager releases prior to VM 8.1.2.2
Project meta-data (.ser files): A project or project database no longer loads and gives a Java exception (most commonly java .io.StreamCorruptedException: invalid stream header). A project starts showing the identical contents of another project.
CMS-XML Click "ALERT: A57" for Java 1.7.x updates solutions for Serena web clients using the Java plug-in may randomly stop working after 14 January 2014.
Due to security enhancements that have been added to Java 7 as of update 25, the release of a new JRE on Oracle's website will automatically block certain features in the older versions of Java plug-ins that may be installed on your system. These blocked features will prevent the web client of certain Serena products from working, such as Dimensions CM and PVCS Version Manager. If you are using Dimensions CM, please see Knowledgebase Solution S140201
CMS-XML McAfee anti-virus update breaks Version Manager by incorrectly flagging it as containing the Exploit-CVE2012-0507 Trojan
SEVERE: Servlet threw load() exception java .lang.ClassNotFoundException: pvcs.vm.servlet.VmServlet at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1701)
CMS-XML HP-UX patch breaks Version Manager running in setuid mode
/usr/lib/dld.sl: Can't open shared library: /CLO/Components/ JAVA _12/Src/build/HP_UX/lib/PA_RISC2.0/server/libjvm.sl
CMS-XML Expiring Certificate for Dimensions CM on 13 June 2015 if you are using Dimensions CM SSO Server with CAC or SmartCard enabled
: For Dimensions 12.2.x and earlier, the jre version is 6.0. If you are on a UNIX or LINUX server, use forward slashes and replace the jre directory path with:
CMS-XML MCLG 4.6: Getting Collage ready for the new USA 2007 Daylight Saving Time rules
Windows: To upgrade to the latest version of JRE 1.4.2x do the following: Go to http://java.sun.com/j2se/1.4.2/download.html
CMS-XML KM-Dim10: Alert - Dimensions CM 10.1.0 and 10.1.1 and Refactoring
For this example, we will assume that there are four stages - "DEVELOPMENT", "UNIT TEST", "SYSTEM TEST" and "RELEASE" each of which have an attached deployment area. Imagine a Dimensions project contains a file called "src/examples/ExampleMain. java ", for which a revision is currently deployed to "UNIT TEST".
CMS-XML Dimensions CM Web Client applet certificates expire on February 25th 2017
The certificates used to sign the Dimensions CM applets will expire on February 25th 2017. After this date users will get a Java security warning when logging into the Web Client or Adminconsole. (Functionality will be normal when a user acknowledges the warning and proceeds).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs