Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Error getting services: org.apache.axis2.AxisFault: Remote host closed connection during handshake
This is because either the IIS SSL certificates has expired or it does not exist at all. To resolve, start Configurator, go to 'IIS Server' tab and either Import New Certificate by clicking on the 'Import New Certificate ' button or Generate a Sample Certificate by clicking on the 'Generate a Sample Certificate ' button. After importing SSL certificate, restart of IIS and JBoss is required.
CMS-XML Meritage -Meritage fails when Tomcat is configured to accept SSL connections only.
... If Meritage Tomcat server has been reconfigured to accept SSL connections only Meritage clients ... The underlying connection was closed: ... relationship for the SSL /TLS secure ... ... - The underlying connection was closed: ... relationship for the SSL /TLS secure ... ... : The underlying connection was closed: ... relationship for the SSL /TLS secure ... ... \addin\ server \webdav\ ... Message: The remote certificate is invalid according to the validation procedure.
CMS-XML / connection to ldaps is failing / OpenSSL error error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure
t1cb8 IO bf16:4d ### ERR handle EIOSSLREAD 4cc58 ukwn Trouble processing events for fd=314456 (e.g. i/o error). Will drop connection. ( accept from 4100 (3))
CMS-XML Dim2009R2: SSO CAC: Error acquiring remote data: SSL handshake failed
In addition, if the above fix does not fix the issue, verify if there is more than one verison of Java installed and that it is pointing to the correct jvm.dll. To determine this, - Run <Tomcat>\bin\\tomcat6w.exe //MS//SerenaTomcat, open Tomcat properties from tray, check Java page and ensure that it points to "<CM>\..\Common Tools\jre\6.0\bin\ server \jvm.dll"
CMS-XML Using SourceBridge from the VM I-Net Web Client when the connection to the SBM server uses HTTPS (Secure Sockets Layer - SSL)
If you would like, you can use the attached Java application TestHTTPS to verify that the JRE keystore now accepts the HTTPS-based URL for the SBM / TeamTrack / Tracker server . To run the application, save the file TestHTTPS.class
CMS-XML Get Internal Server Error (500) when logging into the Application Repository.
Both of these errors indicate some kind of communication problem with JBoss and the database server. In this case the MSSQL server was setup to only accept SSL communication which doesn't cause a problem for the Application Engine database since it uses ODBC and is able to negotiate SSL connections automatically but did become a problem for the other databases that communicate via JDBC like the Repository, Common Log and Orchestration Engine databases. If this appears to be the case in your situation look at this KB S139719 doc for steps on how to remedy.
CMS-XML How to setup SBM to accept email submit of new items (pre-SBM 10.1)
If your email server requires an SSL connection , you must add the SSL Security Certificate (in .PEM format) to SBM. First, save the .pem
CMS-XML Dimensions 14.3.2: Error PRG4700058E when attempting to review change set graphs in pulse
When attempting to access changeset graphs in pulse when using SSL you will run into the error shown below, "PRG4700058E: The request to remote server was not successful; SSL peer certificate or SSH remote key was not OK (51)" This will prevent you from reviewing change set graphs when you have SSL enabled on the server.
CMS-XML How to ignore erroneous SSL with LDAP errors when certificate appears correct. (Certificate common name does not match the host )
There may be a situation where the ssl certificate being used to make a secure LDAP connection appears to be valid by all accounts yet the test connect still won't work. ... Certificate common name does not match the host : error 'Neither subjectAltName extensions nor commonName match' : 0x800b010f ... To avoid the situation when old certificates might not be accepted after WinLDAP adoption by SBM, the mechanism to ignore specific certificate validation errors is provided.
HTML SQL*Plus Report
... _Hashtree2 Node EXECUTE /f ... ... DELETE OL$ NODES DELETE OL$ NODES SELECT OL$ NODES INSERT OL$ NODES UPDATE OLAPIBOOTSTRAP2 ... ... /IPAcl/ Host EXECUTE com/ ... /IPAcl/ Node EXECUTE com/ ... ... /dns/ Tcp ... /ldap/ Connection EXECUTE com/ ... ... /net/ ssl /KeyManager EXECUTE ... /net/ ssl /SSLContext EXECUTE ... /net/ ssl /SSLContextSpi EXECUTE ... /net/ ssl /SSLPermission EXECUTE ... /net/ ssl /SSLSecurity EXECUTE ... /net/ ssl /TrustManager EXECUTE ... /net/ ssl /X509 ...
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs