Locks prevent certain situations that may damage or corrupt Test Generator data or cause unpredictable results from occurring. The following situations are not permissible and are protected by locks:
No user can login to more than one client at once (TG or Tester).
No user can edit a test while any user is taking that test.
No user can edit or take a test while any user is editing the test.
If users attempt to violate these conditions, a prompt informs them they cannot perform that action.
Administrators can view the current locks by selecting System > Locks in the Tree Directory.
Locks are normally enabled and disabled automatically. However, there may be situations, such as a computer crash, in which a Lock stays enabled. In this case, the lock behavior is still evident (the appropriate prompts appear), though the lock may no longer be valid. If so, the lock may need to be deleted manually. Consult a TG Administrator to do this.
Note: Locks should never be deleted under normal circumstances. If a machine crashes during a test, the test taker should be able to log back in to the Tester and resume the test in its current state. Always try this approach first.
If the current lock is not valid, an Administrator must log in and identify the lock under System > Locks in the Tree Directory. Delete the lock by highlighting the row and pressing the Delete key on the keyboard.