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 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 SBM: Deploy fails with "WebService payload size (11998823 bytes) violation" and log gives "An item was expired by the cache while it was locked"
Deploy fails with the following error: Deploying to server "Test Environment" at 6/11/19 9:50 PM. INFO -- Transfer process app "My Process App" to Application Engine Host Test Environment at Tue Jun 11 21:50:06 EDT 2019, by user myName.
CMS-XML 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
CMS-XML 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
CMS-XML 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.
CMS-XML 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>.
CMS-XML 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
CMS-XML 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:
CMS-XML Java 7 Domain Account Locks on windows 7 and XP
Java SE Ver 7 all updates are failing Kerberos Pre_Auth and locking domain user accounts because of truncated UDP packets. When a user opens a page that uses JavaScript their domain account gets a bad password, subsequent openings in the lockout threshold window (5 in 30 minutes for us) results in a domain account lockout This effects XP\Win7 (32Bit browsers with IE 8 and 9)
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs