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 RTM to TestDirector connection times out
After approximately three hours the RTM to Test Director integration will timeout . You will then receive this error message when trying to gather a list of requirements.
CMS-XML VS Studio may exit unexpectedly if user attempts to access data from CM after CAC connection times out
Visual Studio session can exit unexpectedly if opening Serena Explorer or other similar activity after a CAC timeout .
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
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
CMS-XML Dim10: WARNING: inbound connection timed out (ORA-3136)... in Oracle alert logs
Also parameters in sqlnet.ora and listener.ora need to be checked. Setting SQLNET.INBOUND_CONNECT_TIMEOUT and INBOUND_CONNECT_TIMEOUT_listenername to 0 makes the timeout indefinite; the default is 60 sec.
CMS-XML RLC Release Package deployment fails with a Server Unavailable error if a pre-plan step takes longer than the connection timeout value configured in the Nolio plugin configuration.
RLC Release Package deployment fails with a Server Unavailable error if a pre-plan step takes longer than the connection timeout value configured in the Nolio plugin configuration.
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 SBM 10.x database upgrade to SBM 11.x gives error "Failed to upgrade Orchestration Engine database. Connection to the Application Engine server has timed out."
SBM 10.x database upgrade to SBM 11.x gives error "Failed to upgrade Orchestration Engine database. Connection to the Application Engine server has timed out ."
CMS-XML Database connection timeout expired error
OpenEx failed with connect string 'DSN=xxxx;UID=xxxx'. Connection Dead. Timeout expired.
CMS-XML Two database connections opened for job which should have closed due to timeout
The Crystal Cache Server then returns a generic error indicating a general failure of the Crystal Page Server. However, the viewer then makes a second request (a retry) to the next available Page Server thereby opening a second connection to the database (and using a second concurrent database license).
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).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs