How should I proceed after a problem?

Objecteering crashes

1. Re-open the crashed project.

2. At start-up, the teamwork MDAC will automatically try to recover from the crash.

· If the command was a check-in, the teamwork MDAC will automatically undo all operations carried out in the repository. The repository will then be restored to its state before the check-in.

· If Objecteering crashed during the database save after the check-in, a synchronization and an import will be run on the element on which the check-in was run.

· If the command was an undo-checkout or the Objecteering CM Synergy "Delete and replace" command, a synchronization and an import will be run on the element on which the undo-checkout was run.

3. Re-run the command on all elements on which it failed.

4. If Objecteering keeps crashing during the recovery:

· Delete the "userName.sync" file from the "Locks" directory, where "userName" is the user login name used in the repository.

· Make a backup save of your database.

· Run a synchronization.

· Run an import from repository one by one on each element whose state has changed to being checked-in, and save after each import.

Consistency checks

If a model cannot be imported because of consistency checks, you should carry out the following operations:

1. Deactivate consistency checks.

2. Check-out the part of the model causing consistency errors.

3. Correct the model.

4. Activate consistency checks.

5. If consistency checks have been activated, check-in the modified elements.

How can I resolve a problem of dependency cycles?

If two users create a dependency cycle between two packages and validate their actions via the check-in command, then no check-out commands can be carried out on "destination" packages.

To solve this problem, re-run a check-out of the "origin" packages, change the use link into a referencing link and then confirm these changes by carrying out a check-in command.