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 Dim cm 14.4: not possible to login to pulse, getting error "Could not acquire change log lock. Currently locked by () since "
Dim cm 14.4: not possible to login to pulse, getting error "Could not acquire change log lock. Currently locked by () since "
CMS-XML RLC.log gives error: liquibase.exception.LockException: Could not acquire change log lock. (Liquibase FAQ)
... Waiting for changelog lock ... Database is currently locked . ... xml]: Cannot resolve reference to ... ... xml]: Cannot resolve reference to ... Could not acquire change log lock . Currently locked by XXXXX ( ... ... xml]: Cannot resolve reference to ... [rlc-context.xml]: Cannot resolve reference to bean 'entityManagerFactory' while setting bean property 'entityManagerFactory'; ... Could not acquire change log lock . Currently locked by XXXXX (10.10.10.15) ... Reason: Couldn't call external web service 'http://SERVER:8085/rlc/scriptRunnerService
CMS-XML Logging in gives error "The proxy server isn’t responding" and server.log gives "Error creating bean with name 'liquibase' defined in class path resource"
... The proxy server isn’t responding ... 4j- log 4j12 ... ... 4j- log 4j12 ... Could not acquire change log lock . Currently locked by FXBM-WPS-FLM92V (132.9.109.34) since 9/14/16 11:30 AM
CMS-XML User Error: #2 get -l says already locked, put says cannot create log file
CAUSE: the /home directory was changed to 700 (rwx,---,---) by the system admonistrator. This caused the problems with the command line exes
CMS-XML DA: Unable to connect to DA following a change of Oracle password for the DA schema. ORA-28000 found in the Tomcat log.
// number of times specified by the user's profile parameter // FAILED_LOGIN_ATTEMPTS, or the DBA has locked the account // *Action: Wait for PASSWORD_LOCK_TIME or contact DBA
CMS-XML RLC: After log into RLC Plugin Configurator, get: "Error HTTP 404 Not Found"
liquibase.exception.LockException: Could not acquire change log lock .
CMS-XML Release Automation: When attempting to remove a process - Error: Can not open item for edit
To remove the lock , the original editor should log back in, open the process for editing , close out the editing session, than log out. This should remove the lock.
CMS-XML RLC: All of the custom widgets give 404 error "server did not find a current representation for the target resource or is not willing to disclose that one exists"
liquibase.exception.LockException: Could not acquire change log lock .
CMS-XML Release Package shows error "The current or locked environment has invalid tasks. Refer to the System Log for more information."
". This will review each task and check to see if there is required information that is missing. Any tasks that do not have missing required information will change to be black.
CMS-XML KM-Dim10: Defecrt Reported DEF113976: Dim 10: changing item types (MIT) defect
The code that is called to perform the MIT command is running as the user logged into Dimensions and invoking the command, rather than the system user that Dimensions runs as. This means that the MIT command will fail if the Dimensions server is locked down (i.e. if the Dimensions end user has no write access to the box). The problem is that the command will try to run as the logged in user and try to create a temporary file (the library file(s) about to be moved).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs