![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Locked Module not found in Lock Manager Topic Summary: Created On: 18-Feb-2004 17:49 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
DOORS 5.2
I attempted to copy a project and recieved the following error message: Copying [project name] failed. Cannot add locked module to clipboard: [module name] When I open the lock manager I do not see ANY locks in that project at all. If I go to the module specified and open it then close it. The "implied" lock seems to disappear. Why is DOORs telling me that the module is locked and I still can't see it in the Lock Manager? Why is DOORS telling me that the module is locked and it really isn't? |
|
![]() |
|
![]() |
|
We sometimes have the situation that the lock manager does not show anything, but when you check the box Current folder only, the locked module shows up. Sometimes very old locks appear or locks not associated to the current folder. I'm talking DOORS 5.2. Conclusion: it doesn't answer your question, but we have similar strange behaviour of the LM sometimes.
Pieter ------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
|
![]() |
|
Peter,
Thanks for the response but I tried checking the current folder. Then all locks. Closing DOORs etc. I have concluded that there must be an in-between state from being "Officially" locked and "almost" locked. DOOrs checks the "almost locked" parameter and thinks that the module is locked but the lock manager must check a different parameter to display "Officially" locked modules. Hey, that's my guess anyway. The bottom line is that it thinks the modules are locked when in fact they are not. When the person who is supposed to have the module locked attempts to open it, they are allowed to open the file. Then closing the module corrects the mystery of the missing locks. |
|
![]() |
|
![]() |
|
Locks frequently just don't show up in DOORS manage locks window. The information is better when using a Database Admin account but not good. And of course there is the stale locks problem, where some locks really are there but ar not shown. That's DOORS 6 SR1 I'm talking about. I've been told that DOORS 7 is better at this.
|
|
![]() |
|
![]() |
|
Yep, I've been told that DOOR 7.0 does better at stale lock as well. Granted it does seem to do a somewhat better job (particularly when the client crashes and some formal modules are left open). But I have seen the same thing happen on 7.0 SP1 as well...*shrug*
|
|
![]() |
|
![]() |
|
We're using DOORS 8.1 and even now the Lock Manager is flakey. Sometimes a lock won't show up in the lock manager, or the "for Lock in Locklist" loop in DXL code, yet once I try to archive a project, it throws an error saying something is locked! Logging in as Administrator helps a lot, but even then some locks go un-noticed until one tries to archive.
Does anyone know how to make the "for lock in locklist" loop behave consistently?
Jason
|
|
![]() |
|
![]() |
|
I haven't had an issue with it myself in DOORS 8.1. I don't think any of the patches have addressed it but are you running the latest patch of 8.1?
Also if you're on 8.1 now you should go ahead and upgrade to 8.2. Can migrate the 8.2 client out slowly since the 8.1 client will still work and just have to install the new 8.2 server, get a new license from Telelogic, and drag and drop the 8.1 data files into the 8.2 data directory. Of course I say this even though we're still running 8.1 since our IT guys haven't done it yet despite frequent reminders. ------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
It appears some users are expecting to much from the "Manage Lock Window"
Help file gives list of exceptions of why objects don't appear inside the "Manage Lock Window" as follows: The list does not include the locks associated with your current DOORS session, because you must not delete these locks. If you deleted them you would corrupt your data. If you're a Standard user, you only see the items that you locked in previous DOORS sessions. If you're a Database Manager or a Custom user with the power to manage the database, items locked by all database users are displayed. If you have a chain of locks from the root of the database, you only see the lock at the end of the chain. |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Locked Module not found in Lock Manager
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.