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 SBM: How to unlock (break lock) an element in Composer that is locked (checked out) by a different user
SBM: How to unlock ( break lock ) an element in Composer that is locked (checked out) by a different user
CMS-XML Update transition does not work when using Firefox via https - break lock is shown
Update transition does not work when using Firefox via https - break lock is shown
CMS-XML Can't finish item that has not yet been completed - TT tries to break lock
Can't finish item that has not yet been completed - TT tries to break lock
CMS-XML All transitions fail to complete in 11.x if you disable record locking
Lock for this record has been broken : We're sorry, admin, 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 DEV INT: "Error: Failed to lock [filename]" (WSAD 4/VM integration)
DEV INT: "Error: Failed to lock [filename]" (WSAD 4/VM integration)
CMS-XML Problem: : Removing one lock from an archive containing multiple locks on one revision fails
Problem: If a revision is locked by 2 users as in the example below: PVCS Version Manager (vlog) v6.0.10 (Build 24) for Windows NT/80x86
CMS-XML Attempts to lock or unlock any application in ISPF are failing
Attempts to lock or unlock any application (ISPF global admin option A.G.7/panel CMNGBULP) in a ZMF 8.1.4 environment here always results in the DEMO application being selected for processing. For example, I have not yet selected DEMO for any lock or unlock request and these are the log records that have been generated:
CMS-XML Dim CM 2009 R2: Trigger records semaphore lock and fails in certain instances
When using a trigger there are certain instances where the trigger fails . These situations, along with how to recreate them, are described below: -
CMS-XML KM-Dim9:9506-DB_FAILED_TABLE_LOCK  Failed to lock table %s for update
KM-Dim9:9506-DB_FAILED_TABLE_ LOCK Failed to lock table %s for update
CMS-XML Deleting requirements with CSV Import may leave the requirements locked if the import fails.
Using CSV import to delete objects will leave the objects locked if the deletion fails. If this happens, use RM Manage to remove the locks on the objects. RM Manage --> select the project --> right-click --> Administer Locks --> select objects to unlock --> Unlock Selected
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs