Resolution:
Description:
==========
This error indicates that a repository was locked when trying to register the EMS plugin or remove the secondary admin domain. In general, the repository is marked as locked when an administration server accesses a repository for update. This is by design to prevent multiple users from accessing a critical resource at the same time. In some situations, a repository may remain locked although it is actually no longer in use.

Resolution:
=========
For a server-based repository, you can break the lock by setting the repo.forceInstanceLocks property in the tibcoadmin_<domain-name>.tra file to "true" and restart the administration server.

For local file repositories, a lock file exists in the same directory as the project file and has a .lck extension rather than a .dat extension. You can force the removal of a lock on a repository by deleting its .lck file.

For a database based domain, delete all rows in the ADENTITYLOCK and AUENTITYLOCK tables. This action will remove all locks in the domain. Only do this only after making sure there are no other users working on it. Backup the domain database before doing any modification.

NOTE: TIBCO does not recommend manipulating the domain database directly since it may cause a domain crash. Please consult Admin Support before making any changes.

Error message, "Error -- com.tibco.pof.entity.EntityLockedException: Userfailed to lock object with name ... Object was locked by... at ..." when running the Domain Utility.