Hi, What could be the problem? What is 'locking' the project? Thanks in advance. LeireTorres - Mon Apr 11 03:45:35 EDT 2016 |
Re: DOORS cannot move a project If you cannot see the lock when you use the DBSAdmin tool, and archiving does not raise a lock warning, then it seems like you have a rogue lock that has not cleared correctly. This can happen if a users client session ends abnormally whilst a save was being performed, such as when a PC suffers a critical exception event. DOORS also applies locks to the folder path that a module resides in - I'm not sure about version 9.5, but certainly in earlier versions of DOORS it had a problem with clearing up these folder locks after a user had closed a module that they were editing. These residual folder locks would only clear up when the user logged out so see if you can get everyone to log out and see if this helps. I know you have tried using the DBSAdmin tool to see locks, but I would recommend logging into a DOORS client as the Administrator user and have a look at the "Manage Locks" tool just to be sure that it doesn't show any folder locks within that project. Beyond that, stopping and restarting the DOORS database service has been known to clear rogue locks, and if that doesn't work, then it gets more complicated where you have to try and hunt down the lock files (lock.dtc) within the database and delete them. This will require some DXL to help guide you to the locations in the database where you will find the data for each of the modules in your project - this would be a last resort.
Paul Miller |
Re: DOORS cannot move a project
Hi, |