Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
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
Web Client throws missing JRE error on Linux when using Java 7 Update 71 and newer or Java 8 Update 20 and newer
CMS-XML Users other than the setuid user get Exception in thread "main" java.lang.UnsatisfiedLinkError or java: error while loading shared libraries: libjli.so
While trying to launch the GUI or PCLI, one of the following errors is thrown: Exception in thread "main" java.lang.UnsatisfiedLinkError: nativeInitializeUIDs Exception in thread "main" java.lang.UnsatisfiedLinkError: <VM_Dir>/vm/common/java/<OS>/jre/lib/<CPU>/libawt.*
CMS-XML Java HotSpot error on Solaris when adding a workfile that ends with an asterisk
While attempting to add a (collection of) files, the following Java HotSpot error is thrown on a Solaris system: # An unexpected error has been detected by HotSpot Virtual Machine: # SIGSEGV (0xb) at pc=0xefd4393c, pid=29952, tid=14
CMS-XML Removing "null" related errors from a Project Database introduced by using Java 6 Update 10 (or newer) with a VM I-Net web client that did not support it
As of release 8.1.4.0, Version Manager officially supports the use of Sun JRE 1.6.0 in the web browser clients. However, a change introduced by Sun in JRE 1.6.0 Update 10 (1.6.0_10) causes a number of problems when that JRE is used with VM 8.1.4.x.
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)
If a user installs the Java 7 Plug-in ( JRE 1.7.0 or 1.7.0 Update 1) on a PC and then tries to using the VM I-Net 8.4.x web client, the "Wait" button on the login screen never turns to "OK". In addition, the following exception may be shown: basic: exception: java.lang.ExceptionInInitializerError.
CMS-XML VM I-Net server shows Java stackdump errors from Tomcat after upgrading to a newer release
The Serena VM Web Application Server is running as a service. When all these are true, the compiled JSP code that is located in vm\common\tomcat\work will continue to be that of the previous version, which can result in unpredictable errors due to the incompatibility with the newer JSP pages that were just installed. An example of an error cause by this problem:
CMS-XML Error: MS Error 2140 while trying to start SUN Java WebServer
Don't know a lot about this one yet. Apparently there is a MS* .dll which sets a Class Path Variable that causes a conflict with the SUN Java WebServer, preventing it from fully installing. You will see a note about the CLASS PATH VARIABLE error if you run the command HTTPD -verbose...
CMS-XML VSS2VM: When running a migration and the VSS project structure is nested ~11+ levels deep the migration gives Java Hotspot errors
$/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/a.txt The hotspot errors will be much like the following: An unrecoverable stack overflow has occurred.
CMS-XML VMInet 8.3 & TT 66117 - Sourcebridge / Java throws an error 46
Click on OK button and redo all the steps again- same popup would be displayed. Current problem is that with each upgrade of Java - the "Enable next generation Java plugin" is re-enabled. This is causing Sourcebridge to fail with VM 8.3 and TT 6.6.1
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.
If users other than the PVCS user get this error , and the PVCS user does not get this error , the symbolic links may not have been created correctly, as described in the readmevm.txt file.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs