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 UpdateWithLock() appscript method doesn't lock item so it fails
line 4182. Resource Msg Id = IDS_MSG_ LOCKS _RECORDMUSTBELOCKEDBEFOREUPDATE The user must have the record locked before update. Instead of using UpdateWithLock() you will want to use the Lock() method, do your update, and then use UnLock() method.
CMS-XML Import process locked
If an import fails in the Application Administrator then the import process is not released and an error message is received telling the user the Process is still in use and therefore locked . The user can not run the import process again until the system is restarted.<\p>>
CMS-XML RLC.log gives error: liquibase.exception.LockException: Could not acquire change log lock. (Liquibase FAQ)
Context initialization failed
CMS-XML Importing Release Control solution gives "Failed to extract the solution. You do not have permission to delete the obsolete snapshot"
Log into the Application Repository ( http://server:8085/mashupmgr ). Switch to the Privileges view. Select your user, and verify that you have all privileges, including Delete Process App, Delete App/Orch, and Break Lock .
CMS-XML Decision step operation fails during automatic execution
Lock for this record has been broken : We're sorry, Chad Support, but your lock on this record was broken . By using the back button you may be able to see the changes you were about to make. If your data has been cleared please re-enter it.
CMS-XML No prompt to save changes before advancing to next item in Manage Aux Data view
When editing an entry in an aux table under the Manage Auxiliary Data section of the Application Administrator, a prompt is not thrown to save changes if you try to advance to the next or previous item using the navigation buttons at the bottom if you forget to hit the 'Update' button before doing so. This will effectively place a lock on the item which you'll have to break .
MS-WORD S141325-Upgrading to Release Control 6.0 WITH Using Old Data.docx
Switch to the Privileges view. Select your user, and verify that you have all privileges, including Delete Process App, Delete App/Orch, and Break Lock . Continue with STEP 3 : Install Release Control 6.0.
CMS-XML No longer able to make changes to an existing Deployment Path
I can understand that you don't want the environments in the path to change, if there are active RPs. But, you should be able to change the redeploy option, the lock option, fail path, required flag, etc.
CMS-XML Error "Please check selected SRA application history. Request Status Failed."
<!--This will give out the timout of the configuration contexts, in seconds--> <parameter name="ConfigContextTimeoutInterval" locked ="false">120</parameter> ... <!--This will give out the timout of the configuration contexts, in seconds--> <parameter name="ConfigContextTimeoutInterval" locked ="false">120000</parameter>
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"
Initialization of bean failed ; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in class path resource [rlc-liquibase-context.xml]: Invocation of init method failed ; nested exception is liquibase.exception.LockException: Could not acquire change log lock . Currently locked by FXBM-WPS-FLM92V (132.9.109.34) since 9/14/16 11:30 AM
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs