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 VM I-Net server may lock up with Resource Locked by Session errors when using LDAP login with referrals
VM I-Net server may lock up with Resource Locked by Session errors when using LDAP login with referrals
CMS-XML VM I-Net login locks up for all users ("Wait" / "Resource locked by Session")
VM I-Net login locks up for all users ("Wait" / " Resource locked by Session")
CMS-XML An exception occurred while attempting to calculate the next ID number to be used for the "table" - error: Unable to get next id for tableid ... Transaction was deadlocked on lock resources with another process and has been chosen as the deadlock victim
An exception occurred while attempting to calculate the next ID number to be used for the "table" - error: Unable to get next id for tableid ... Transaction was deadlocked on lock resources with another process and has been chosen as the deadlock victim
CMS-XML VM 8.1.x - 8.2.1 - Version Manager Web Client (VM I-Net) users denied login with error "The resource is locked by session "
(on UNIX) contains the following error message: ResourceLock. lock () - *** Attempt to unlock object not locked by this session (may not be locked ) (On Windows, if the Serena VM Web Application Server is not running as a service, the message shows up in the console window titled Serena VM Application Server.)
CMS-XML VM I-Net Web Client users get the error "Resource is locked by session ###"
Intermittent resource lock errors typically indicate slowness accessing one or more of the resources used by the Project Databases:
CMS-XML VM I-Net LDAP users still see session lock errors / LDAP_BIND does not honor timeout
VM I-Net users of project databases that use the LDAP login source are randomly experiencing login failures, or failures to perform certain operations (Get, Put, Label, etc.), with the feedback messages indicating session lock errors ( Resource Locked by Session). When this problem occurs it can affect numerous users and last for an unspecified amount of time, sometimes until
CMS-XML err saying "ora-00054 resource busy and acquire with no wait specified"
At TT admin interface, check File|AdministrativeLock or File|RecordLock to see if any locks there? If there is any lock, remove the lock, then have a try again.
CMS-XML Error: Internal error # 10 When Trying to Checkout With A Lock.
The user could perform an archive report, could checkout read-only, and could checkout other files with a lock. Other users were unable to checkout this one file with a lock also. They were using only 16 % of there systems resources .
CMS-XML What does "Error starting static Resources" error mean in tomcat.log?
java.lang.IllegalArgumentException: Document base C:\Program Files\Serena\SBM\Common\Tomcat 7.0\server\default\webapps- locked \..\webapps\acmeapp does not exist or is not a readable directory
CMS-XML Problem: File in Use or Access Denied # of Retries, problem with NFS and locking.
NFS Maestro Gateway or NFS Maestro Client, the problem could be with NT and file locking. Resources in use are usually locked by
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs