![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: How to know what users are on the DOORS server Topic Summary: Created On: 31-Aug-2006 03:01 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
When archiving a project, the administrator doing the archiving must ensure that all users are out of the project. Currently, the only way we know to do this is to try the archive and see if we get a message that the project is open to one or more users. When we get a message, we go around to each potential user, trying to find the ones actually in a project. This seems inefficient.
Is there a means for an administrator to determine what user accounts are in use? Thanks in advance |
|
![]() |
|
![]() |
|
Hi Kent,
in Doors main menu, you can find an entry "Tools/Manage Locks". There you can see who is blocking you archive action. But this functionality is only available for database administrators. Greetings Reik ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
If I use Tools -> Manage Locks, I get a list of folders as long as my arm, with MAYBE a couple of module locks.
Some of the locks are obviously out-of-date and it appears DOORS v7.1 doesn't tidy up locked folders correctly and may even add folder-locking just because the user has logged in. Anyway, it's the module-locks you need to know about, but ability to sort the list on any of the columns would be really handy, especially if I wanted to tidy up some erroneous locks. |
|
![]() |
|
![]() |
|
Use the 'dbsadmin.exe' tool, probably located on your server in the '..\DOORS X.X\bin' folder. Not only can you see who is logged on (and may not be in a module, so they don't show up in the locks list), but you can kick them off if you can't get a hold of them (Like they logged in and then went home).
------------------------- Bob Mathis Robert.S.MATHIS@odot.state.or.us |
|
![]() |
|
![]() |
|
Thanks, Bob. That looks like what I need. BTW, it's been a long time since the Ada9X activities, eh?
|
|
![]() |
|
![]() |
|
Thanks for your reply, Reik.
Unfortunately, for archiving purposes, it seems that a user can block the archiving even if they don't have any modules open. All they have to do is have their DOORS Explorer inside the project you want to archive. When we look at the Manage Locks tool, none of the users that are in our way show up. Kent |
|
![]() |
|
![]() |
|
Hi Kent,
did you tried to unckeck the "current folder only" checkbox? And of course use refresh button... I never had problems with finding out the user who locks an item in that way?! ![]() When user has opend a folder the lock should be displayed there... Greetings Reik P.S.: of course you could create your own DXl script to show more information about the locking users (email or phone number). Therefore you can use the for lock in lock list loop. Please refer to reference manual to this topic. p.s.: In my last job, I have done the archiving in night and unlocked all users before. But there are some difficulties of doing that. You can prevent users from login into database by changing login policy in database properties. But the problem is, if the user does not logout, (s)he can not prevented from login. ![]() ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
Thanks for the reply, Reik. |
|
![]() |
|
![]() |
|
Hi Kent,
could it be possible, that you have opened something in background yourself (a link module for example)? Sometimes I had exactly this problem - I have prevented me myself from archiving ![]() You can see all open Modules in "Tools/Manage Open Modules" dialog ... And it is really important to have database adminitrator rights to see locks from other users. If you do not have these rights, you will only see your own locks (but not from current session!). I have tested the scenario. One user is logged on and the database browser is in a project, but no module is open. Then I logged in as Administrator and had a look into Manage Locks dialog and it shows, that the one user is locking the project. Greetings Reik ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
Hello,
There are sometimes "lost" locks, which are not visible in lock list. Only way to see them (and release them) is to use dbadmin tool. Following commands may help you: To list all logged users: dbadmin -data <port>@<server> -userlist To list database locks: dbadmin -data <port>@<server> -locklist To kick user: dbadmin -data <port>@<server> -killprocess <ID> To unlock file: dbadmin -data <port>@<server> -unlock <ID> More information about dbadmin can be found in DOORS help file, section: "Managing the database server". Rafal |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.