| |
Results |
|
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
|
|
|
|
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
|
|
|
|
Problem: HTTP Error 401 401.1 Unauthorized: Logon Failed or HTTP Server Error 500 Referenced account locked and cannot be logged into.
|
HTTP Server Error 500 Referenced account locked and cannot be logged into. HTTP Error 401
|
|
|
|
vcs_make -> Failed to acquire make lock, another make is still running
|
There is a mechanism in place for assuring that a similar make is not running for a given project at the same time. There is a record in the vcs18 table which includes fields for the make procedure name and project name as well as a lock field which represents the time when the "make" was launched. When the "make" procedure ends, the lock is released by resetting the value to "0".
|
|
|
|
Dim12: Failed to connect to the Dimensions server - ACL4502922E Error: Cannot open connection to host HOSTNAME - DBI0004527E DBIO: Database I/O error occurred ORA-28000: the account is locked
|
Logging into Dimensions, the following error message is returned: Failed to connect to the Dimensions server. ACL4502922E Error: Cannot open connection to host HOSTNAME
|
|
|
|
Dim12.x: Deployment: Unable connect to database + Failed to lock database + Failed to connect to database
|
2013/02/11 08:53:58 UTC 1.052 T T885561088 DDeployService::connectToDb: Connecting to database < dbname@sid > on host ... as user <userid>... 2013/02/11 09:03:00 UTC 542.379 T T885561088 DDeployServiceLockImpl::acquire: Error: Unable connect to database < dbname@sid > on host ... in order to lock it.
|
|
|
|
VM 8.4.6: HotFix to resolve mutexError (pvcs.exception.FsMutexException,failed to lock lockable) and/or random lockups of the File Server clients
|
Mutex error: "failed to lock lockable" or find that the VM desktop client GUI locked up. These errors could lead to a need to restart the Serena VM Web Application Server or the VM client experiencing the problem.
|
|
|
|
Dim12: Deploy: Deploy server fails when starting with this error "Error: Unable connect to database @ on host in order to lock it."
|
DDeployService::connectToDb: Connecting to database <dbname>@<sid> on host <hostname> local as user dmsys ... DDeployServiceLockImpl::acquire: Error: Unable connect to database <dbname>@<sid> on host <hostname> in order to lock it. DDeployServiceLockImpl::acquire: Failed to lock database <dbname>@<sid> on host <hostname>.
|
|
|
|
Lock for this transition has been broken. We're sorry,, but your lock on this record was broken. The transition "X" was not completed
|
Lock for this transition has been broken. We're sorry,, but your lock on this record was broken . The transition "X" was not completed
|
|
|
|
Deploy-locked TeamTrack database - users must only be edited through their web profile
|
If a database has been locked with the DeploymentTool.exe by the Administrator, so that changes can be made to the database, the user settings can not be changed through the TeamTrack Administrator without breaking the sync between the live and test database. This synchronisation can be checked like in this example:
|
|
|
