Find Answers

Filter Search Results
All Products:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Static Diagnostics Notification Server and Mail client database connection fails if TLS 1.0 is disabled
Steps to reproduce: - Create SSL certificates for both IIS and Tomcat - disable http for IIS and Tomcat
CMS-XML Trying to connect Composer using Secure SSL Connection get error "The request was aborted: Could not create SSL/TLS secure channel"
If you try to connect Composer to the repository using a secure connection, you may get the following errors when it tries to connect. This would by default try to use the 8243 JBoss/ Tomcat port.
CMS-XML KM-Dim9: How to enable SSL on Tomcat
<Factory className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory" clientAuth="false" keystoreFile="C:\Serena\ChangeMan\Dimensions\9.1\CA\keystore" protocol=" TLS " />
CMS-XML Dim14: Installation: Serena Common Tomcat is not installing as expected
Dimensions CM 14. 1.0 .1
CMS-XML Tomcat catalina log shows Error "SEVERE: Error starting static Resources" when the File Server component was not installed
PVCS Version Manager 8. 1.0
CMS-XML KM-Dim10: Reported Defect DEF106431: Issue Fixed in Dimensions 10.1.1: After installing Dimensions 10.1 on Windows, unable to access Web Client and Admin Console. Serena Common Tomcat service won't stay started.
Dimensions CM 10. 1.0
CMS-XML MCLG: After upgrade to 5.1.2, get error 500 in browser and error "options.bat does not exist" in Tomcat log
Upgrades directly to 5.1.2 will work fine. For example, if you upgrade directly from Collage 5. 1.0 to 5.1.2, the upgrade will complete correctly. Also, upgrading from a full install of Collage 5.1.1 to 5.1.2 will complete correctly.
CMS-XML Event Response Code: 500 following the implementation of ChangeMan ZMF 8.2 Patch 3 - REST API (Revision-1)
After the customer disabled their AT-TLS rule, the problem was eliminated. They had the AT- TLS rule encrypting all ports AND they had configured Tomcat to secure ports (HTTPS), so it appears that their issue was caused by double encryption.
CMS-XML Illegal access: this web application instance has been stopped already
In PVCS Version Manager - versions 8. 1.0 through, the Tomcat parameter "reloadable" is set to "true" for the web applications used by the Serena VM Web Application Server. In rare instances, this causes excessive repeated logging of the following error message:
CMS-XML KM-Dim10: Reported Defect DEF106668: After Command Center patch in Dimensions patch, the port is set as default 8080.
The user has changed the tomcat port to 8088 and did not use default 8080. But after executing the Command Center patch in Dimensions, the port is changed to default 8080.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs