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 "ORA-28040: No matching authentication protocol" when connecting to Oracle
ODBC connection to Oracle fails, and the following error appears when you attempt to connect to an Oracle 12c, 18c and 19c databases: [SBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-28040: No matching authentication protocol When you attempt a test connection on the Database Server tab in SBM Configurator, it will fail as well.
CMS-XML MCLG: MVR: Error "ChangeMan Mover Agent exited the connection, Protocol negotiations failed, Credential does not allow authorized access."
Mover Agent test connect returns: " Connection To Mover/Collage Agent Failed ChangeMan Mover Agent exited the connection, Protocol negotiations failed, Credential does not allow authorized access."
CMS-XML PRO8 TRKINET Database information is not complete. Error: SQL state = 08003 (Microsoft) ODBC driver manager Connection Not Open
+++++++++++++++++++++++++++++++++++++++++ In the Tracker I-Net configuration page enter "<Oracle server name>; PORT=<prot_number>; SID=<sid name>" for the DBMS location using the Oracle Wire driver and/or the Oracle 8 driver. Additional Note:
CMS-XML WebSocket console error, can't connect to Deployment Automation using proxy HTTP protocol
Use these to determine if you may need to configure your proxy server to resolve any WebSocket issues when connecting to Deployment Automation through a proxy server. Explicit Proxy Servers with Unencrypted WebSocket Connections
CMS-XML SBM performance issue with Virtual machines
It is possible that the VMware image has stale ARP cache. Address resolution issues will manifest itself in the SBM logs as ' Protocol Error in TDS Stream' or 'unable to connect' or ' Connection Refused', 'Cannot open the database' , 'SQL Error 0, 'Network error IOException: Connection timed out:'
CMS-XML Agents don't appear online after a server upgrade to Deployment Automation version 6.1.1 or higher
6.1.1, Serena Deployment Automation (SDA) has enhanced security to connect through TLS1.2,TLS1.1, or TLS1.0 protocols supported by Java 6 and above, and rejects connection through earlier SSL protocols such as SSLv3 and SSLv2Hello. If you have agents that have been connecting using one of the rejected protocols , your agents may try to connect through the unsupported protocol and the connection will be rejected.
CMS-XML SSL 3.0 Vulnerability - Poodle and Beast - PVCS Version Manager - How to disable SSLv3 and optionally TLSv1
This is the result of a flaw in the SSL 3.0 protocol, and the specific attack may allow a man-in-the-middle to intercept parts of SSL-encrypted communications. Can be mitigated by forbidding SSL3 protocol for HTTPS connections .
CMS-XML How to setup an Apache Reverse Proxy to access a VM I-Net Web Client server running VM 8.6.1 or newer
Starting with VM 8.6.1, the Agent process running on the end-user's PC uses the WebSocket protocol to connect to the server. A WebSocket connection is established via an HTTP protocol upgrade, and additional configuration is require to pass this through a reverse proxy.
CMS-XML SBM Java Notification Server: Migrating from MAPI to Exchange
protocol is also available for use with the Mail Client in the event your company does not allow connection through POP3 or IMAP. If no such restrictions exists, consider choosing
MS-WORD Requirements for load balancer in a Tomcat cluster %2811 0%29.docx
For the back-end connections , the load balancer can use one of the following protocols : HTTP, HTTPS, or AJP. By default, all Tomcat servers are configured to listen for incoming connections on HTTP port 8085 HTTP and on HTTPS port 8243. If AJP is used, the default port is 6009.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs