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 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 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 How To: #814: Troubleshooting an Oracle 7 connection
driver_prefix is a letter identifying the network protocol being used. The driver prefix can be as follows: P (named pipes), X (SPX), B (NetBIOS), T (TCP/IP), D (DECNet), A (Oracle Async), or AT (AppleTalk). Check your Oracle documentation for other protocols.
CMS-XML How To: #53813: Troubleshooting a SQL Server connection
2. Check that the Network protocol has been loaded in memory using the DOS 5.0 command MEM /C | MORE or the DOS 6.0 command MEM /M:NETBIOS from the DOS command prompt to check NetBIOS, or IPXODI, or TCP/IP. 3. Was the driver installed during the Tracker installation? look for the files TKSS07.DLL, TKBAS07.DLL and TKUTL07.DLL
CMS-XML Contrary to Documentation Oracle 8 is not Supported in 5.7 - it is known not to work.
[Data Direct][ODBC Oracle Wire Protocol driver](Oracle) ORA-00933: SQL Command not properly ended. This happens when trying to view attachements to a frozen release.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs