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 PVCS Version Manager mitigation of 'log4j2' compromise - CVE-2021-44228
For older PVCS Version Manager 8.6 .x releases, please follow the steps below. Be warned that using older PVCS VM releases may expose you to other vulnerabilities that have since been resolved.
CMS-XML Is log4j 1.2.17 in PVCS Version Manager affected by CVE-2021-4104 or CVE-2022-23302?
Doing so will break the installation. Even though VM 8.6.3 is not affected by known vulnerabilities involving log4j 1.2.17, Micro Focus will replace that code in the upcoming VM 8.6.3.3 patch, expected to be released soon. If you are running a Version Manager release prior to 8.6 .3 and are concerned about security vulnerabilities, please upgrade to PVCS VM 8.6 .3 (or newer) and install the latest patch available for that release.
CMS-XML VM 8.6.3: After installing the VM 8.6.3.2 patch on Windows, certool fails with java.lang.NoClassDefFoundError
As a result, certtool can fail with the error: C:\>certtool Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/ logging / log 4 j /spi/ExtendedLoggerWrapper
CMS-XML VM 8.6.1: In-place upgrade from VM 8.6.0 fails with Restore report showing a failure for the file gatekeeper-core-config.xml
20190415-165040: File copied successfully. ('D:\PVCS\Serena\bkstore\restores\1904051219.75F\files\common\pvcsprop\pvcs\ vm \sso\ log 4 j .properties' -> 'D:\PVCS\Serena\ vm \common\pvcsprop\pvcs\ vm \sso\ log 4 j .properties'
CMS-XML log4j warning in serena vm application server
PVCS Version Manager 8.4.5
CMS-XML VM: log4j:ERROR Failed to flush writer, java.io.InterruptedIOException
If this is not the issue, and the VM release being used is VM 8.4.x or older, then the error is related to the version of a 3rd party logging module used by those VM release (log4j prior to 1.2.15). VM 8.5.0 and newer include an updated version of this module that is reported to no longer have this issue.
CMS-XML IDE: Enabling logging with the Rich Integration to the Eclipse workbench
To troubleshoot issues with the Rich Integration to Eclipse with VM , the Apache log 4 j logging services can be configured to capture helpful information. In the installation directory for VM, under the /vm/integrations/eclipse/plugins/com.serena.team.core_3.1.0 folder, there is a file named "log4j.properties
CMS-XML VM 8.5.x cannot open SSO based Project Databases from SCC-based IDEs
If it does not already exist, create a sub-directory called patch Copy the file log 4 j -1.2.16.jar , located in the current directory, into the folder patch, so you end up with the file VM_Install_Dir
CMS-XML VM: certtool throws error and stack dump if the current directory is not writable
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:138) at org.apache.logging. log4j .core.impl.Log 4 jContextFactory.getContext( Log 4 jContextFactory.java:147) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:41)
CMS-XML VM 8.4.x on UNIX / Linux lacks sso-gatekeeper.log file
Until this defect has been fixed, the problem can be resolved by manually updating the line: log 4 j .appender.LOGFILE.File=${jboss.server.home.dir}/ log /sso-gatekeeper. log in this file such that it reads:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs