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 Dim14: Pulse: When attempting to log into Pulse, an error of PRG4700066E Serena Pulse is not responding may occur
where scmuri = 'scm:dimensions:id:BASEDATABASENAME@OLDSERVERNAME-SID'; commit; 4. When done, just restart the client which was having problems logging into Pulse .
CMS-XML Dim14: Pulse: How to generate additional debug information in the log files for Pulse
If you need to generate additional debug information to investigate Pulse problems, update the $ Pulse \conf\ logback.xml file by changing the following line from:
CMS-XML PRG4700066E - Serena Pulse is not responding
Logging to Pulse via web for example <hostname>:8080/ pulse /login.html Select Administration
CMS-XML Dim cm 14.4: not possible to login to pulse, getting error "Could not acquire change log lock. Currently locked by () since "
Possible causes of the lock are : a_ If Pulse has been started and it freezes forever, there might be a Liquibase database lock.
CMS-XML DimCM: Pulse: Pages in Pulse fail to load, hang or return various errors.
Debugging some of the failing Pulse pages returns the following error message: {"_exception":"com.serena.starlight.platform.support.resource.ValidationWebApplicationException","detailedErrorMessage":"Pool exhausted","_form":"com.serena.starlight.rest.exceptions.CONNECT_CM"} Pulse logs include Java errors with the following: Caused by: java.sql.SQLException: Connection oracle.jdbc.driver.T4CConnection@5797db2g is closed.
CMS-XML Problem: User logs into Tracker and gets a Choose Profile box. How do we stop this from occurring?
Problem: User logs into Tracker and gets a Choose Profile box. How do we stop this from occurring?
CMS-XML Deploy status says "waiting". Deploy log shows a hang after "Awaiting Callback from Application Engine"
A deploy can sometimes appear to be stuck or hang . In the Repository (Mashup Manager), on the Activities screen, the deploy will have a status of "waiting". The last line in the Activity log for this deploy, will show:
CMS-XML Dim CM 14.x: Session activation failed for user dmsys, connecting to cm_typical@DIM10 with PULSE-WEB from nodename (6)
Usually this file is renamed to backupOnce-!firstRun.js.bak once Pulse is set up. It's not clear why this didn't happen on this installation. Once the file was renamed and Tomcat restarted the Windows Event Viewer and listener log entries stopped being generated.
CMS-XML Dim14: CMBridge: How to generate additional debug information in the log files for CM Bridge
If you need to generate additional debug information to investigate CM Bridge problems, update the $Bridge\conf\ logback.xml file by changing the following line from:
CMS-XML DimCM: Git Client: How to generate additional debug information in the logs for the Git Client
If you need to generate additional debug information to investigate Git Client problems, update the $Git_Client\ logback.xml file: Change INFO to DEBUG for debugging issues: From:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs