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 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 ORA-01115: IO error reading block from file 7 (block # 150057)
[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]ORA-01115: IO error reading block from file 7 (block # 150057) ... The customer could redefine the Tracker Source and test the connection successfully, but Tracker would still give the error if users tried to login it from GUI normally.
CMS-XML KM-Dim9: Replicator: Received connection request for protocol version.
KM-Dim9: Replicator: Received connection request for protocol version.
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 KM-Dim7: Error: Connection refused by . Check status of Dimensions Network
1) Check in Network Node Registration and make sure pcms_dfs is defined as the NETWORK OBJECT NAME and TCP/IP is defined as the NETWORK PROTOCOL . 2) Stop and start Dimensions Network services. If this is a UNIX server
CMS-XML TT 66 - Web Services "The server committed an HTTP protocol violation"
This occurred once a new Oracle driver was applied (10.2.0.1) - it may also occur with other drivers. Since applying this new Oracle driver they are getting the following message when TT makes to first webservice connection .
CMS-XML Dim: Oracle cannot connect: ORA-12537 TNS:connection closed
(ADDRESS = ( PROTOCOL = TCP)(HOST = stl-sup-rh6.serena.com)(PORT = 1521))
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:'
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs