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 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 Meritage -Meritage fails when Tomcat is configured to accept SSL connections only.
The underlying connection was closed: Could not establish trust relationship for the SSL/ TLS secure channel. Additionally, in .\Documents and Settings\<User_ID>\Application Data\Serena\Meritage\meritage.log the following will be found: 2005-07-12 11:54:18,777 [3908] INFO Merant.DocShare.UI.Forms.ServerSetupForm - The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
CMS-XML Deploy stays in waiting when TLS 1.0 is removed from server.xml - Invoking import callback failed: Error observed by underlying SSL/TLS BIO: No such file or directory
As of SBM 11.3, it doesn't look possible to remove TLS 1.0 from both the Server.xml ( Tomcat ) and the SChannel Registry key ( IIS ) and have deploys reach the "Completed" status. The deploy itself will succeed and your changes will get deployed. It is just the callback from the Application Engine to the Repository telling the system the deploy completed that fails so the status stays in "Waiting" forever.
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 Composer cannot connect to the Repository - Error: ... Failed to retrieve valid security token ... could not establish trust relationship for the SSL/TLS secure channel with authority
If you are not using SSL then in Configurator deselecct the SSL configuration for Tomcat . Untick "Use HTTPS on Port" and Apply.
CMS-XML OE database fails to upgrade: Tomcat server startup timed out
Tomcat server startup timed out. ---> ConfigurationUtility.Core.Network.HttpException: URL: https://sbmp02/, Method: GET, Error message: The request was aborted: Could not create SSL/ TLS secure channel.
CMS-XML DimCM: Tomcat: org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header error shows in the Catalina logfile.
This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website's owner.
CMS-XML ALF Events from Dimensions CM are not Received when SBM Tomcat Requires HTTPS (SBM 11.0 or Higher)
For example: <!-- SSL/ TLS Connector for 1-way SSL authentication--> <!-- In Configurator "Tomcat Server / HTTPS Connector 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 How-To Setup SBM on a TLS hardened server / Disable SSL
Secure SSL and TLS in SBM 11.x common_config.bat located in [SBM INSTALL DIR]\SBM\Common\ Tomcat 7.0\bin Locate the section starting with this line:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs