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 KM-Dim9: Getting "Session Expired" from Desktop Client on second and subsequent connection attempts
Remote users are able to connect to Dimensions with desktop client once. On second and subsequent attempts, after completing the login screen they get error "Session Expired".
CMS-XML MCLG 5.1+: How to setup client session timeout
The maximum about of time, in seconds, ANY client (ie WebDav, API connection , browser, etc) can be inactive before the session will timeout . The default value is 180 seconds.
CMS-XML Dim : dmappsrv process start-up fails with this error message : "VRS: compaction on client timeout failed"
DMAPPSRV 2017/02/07 16:35:21 T P2640 T3976 Accepted a client from pool manager DMAPPSRV 2017/02/07 16:35:21 T P2640 T3976 PcmsAccept api connection 4 DMAPPSRV 2017/02/07 16:35:21 T P2640 T3976 Calling initNewClient()
CMS-XML Error: [Intersolv][ODBC SQL Server Driver]ct_connect(): user api layer: internal client library error: read from the server has timed out
User gets following errors during logon to Tracker or Tracker Admin on Sybase DBMS: 1) Database Error: An error while attempting to connect to the database... 2) Invalid attribute in connection string WKID, 3) Invalid attribute in connection string SERVER, and 4) the error message in the title above.
CMS-XML KM-Dim7: Fetch of items appears to 'hang'. Following errors captured in DFS log.pcms_sdp on servername>: Message loop failure LCNetRavRead: read error errno 145145 is ETIMEDOUT (Connection timed out) according errno.h
Check network connectivity(specifically file transfer). between the client and server machines.
CMS-XML KM-Dim10: Reported Defect DEF109853: Timeout for Admnconsole and Web Client not working correctly
Dimensions server is closing the network connection to the client intermittently and this causes the web client to just start returning no data.
CMS-XML DIM CM: Desktop Client closes with an exception error are timeout
When the Desktop Client connection was terminated due to a time out issue and the user logs back in it can happen that Desktop Client closes with an exception error.
CMS-XML Dim10: Desktop Client errors after session timeout and logon cancel
6. The client comes up, but then presents the '... connection to the server has lapsed...' box again. Input the password here and click OK
CMS-XML Time out when connecting to an old Oracle SID
If you change or upgrade your Oracle instance, chance is that you will cahnge the SID name (for example from a SID called DIM10 to a new one called DIM12). If a user tries to connect using a Dimensions client and uses the wrong oracle SID ( connection id DIM10) by mistake, this cause the subsequent connections to hang and wait for a lot of time (it seems that the port of the listener is busy until a timeout).
CMS-XML SRA: Validation of WS-Federation token failed with code 10:Token is expired.
In this specific instance the client machine was found to be 1 hour slower than the SSO server and once the time was corrected the connection could be made.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs