DOORS Module corruption - repeating problem - PLEASE HELP .. :(

Hi

I have users who do not wait out the module to save, and, well, if the need to do whatever it is they are set to do, they just kill the DOORS Session in the midst of the save - thus possibly (from time to time ) corrupting the module.

ofcourse this may also be due to a user with a faulty network connection.

now, my question is -

  • How can I know who caused the corruption - so that I can further investigate the reason * ?

the users are told, naturally, to contact us whenever an error occures and report to us the error - so that it will give us , possibly, a lead. (and to save properly, ofcourse).

still the corruptions continue - we've had three in the past few days - same module, same users.
none of the other hundreds of modules get corrupted every so often - if at all.

Please help :)
Dan_Me - Tue Nov 30 04:34:57 EST 2010

Re: DOORS Module corruption - repeating problem - PLEASE HELP .. :(
llandale - Tue Nov 30 19:04:15 EST 2010

The Module Properties>History tab, select 'sessions', lets you see who opened the module Edit or Share even if no changes are made and the module not saved.

This sounds like to me the module is corrupted and remains corrupted despite your un-corruption efforts (curious what they may be), seems unlikely that a particular module BECOMES corrupted over and over.

Aborting during a save should not 'corrupt', but who knows for sure.

You may want to tell us what the symptoms are and what you did to fix them

  • Louie

Re: DOORS Module corruption - repeating problem - PLEASE HELP .. :(
llandale - Tue Nov 30 19:09:29 EST 2010

... maybe I'll write a 'ExitDoorsFriendly.dxl' script that saves all modules, closes them all, then exits DOORS; and I can do it in such a manner that it leaves a Notepad file displayed summarizing what happened, including trapped errors.

Here are some other possible names:
Exit_Doors_ForMorons.dxl
SaveAllCloseAllExit_ForLazyFolks.dxl
HaveNiceDay.dxl
CYa_Mamma'sCalling.dxl
GTG.dxl

  • Louie