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 PVCS Tracker 7.1.11
... Server with Oracle Wire ... of the Oracle Wire Protocol drivers, end ... ... .1 Oracle Wire ODBC Driver, ... ... use the Oracle Wire Driver with Oracle ... ... Server with Oracle Wire When using Oracle Wire with I- ... enter the following connection string in the ... 5.1.56 (TRK 7.1SP3) Notify User - Description Field Looses Data [1034764] When notifying a user using SMTP protocol , the description field of the SCR is missing in the recipient's e-mail.
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 KM-Dim7: Is there another protocol other than SQLNET that may be used as a workaround for remote_OS_authentication for users over SQLNET. Yes, turn remote_os_authent off and do DBA operations from the Server or enable a BEQ connection for Process Modeler.
KM-Dim7: Is there another protocol other than SQLNET that may be used as a workaround for remote_OS_authentication for users over SQLNET. Yes, turn remote_os_authent off and do DBA operations from the Server or enable a BEQ connection for Process Modeler.
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 HTTP Protocol Violation from WebServices call
" System.Net.WebException: The underlying connection was closed: The server committed an HTTP protocol violation."
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 TRK: Sybase connection using PVCS Tracker 4.1 Sybase ASE driver requires port number to be set
When using PVCS Tracker 4.1 Sybase ASE driver, enable for the connection to be establish, the port number need to be set in the server definition. However, in Server Wizard, when the DBMS Type is set to Tracker Sybase ASE or Sys, there is not an option for setting the port number like Tracker Oracle Wire .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs