DOORS Error when opening Module

Has anyone received the error in the attached file? All other modules in the project work except for this one.
vppatel - Wed Aug 11 13:09:58 EDT 2010

Re: DOORS Error when opening Module
llandale - Thu Aug 12 19:27:06 EDT 2010

Looks like corruption. Try the Integrity Checker, which won't fix it. Try having some admin go to that folder location, and find the corresponding 'treedata.dtb' file (where 'b' stands for 'backup'), and rename it to 'treedata.dtc' (where 'c' stands for 'current'). Otherwise, call IBM and let them give you the run-around.

Louie

Re: DOORS Error when opening Module
SystemAdmin - Thu Aug 12 20:04:36 EDT 2010

Ouch, that looks rather nasty. I would advise getting your IT people to start looking at the back-ups to see if they can find this missing file and exactly when it disappeared. They will also need to check that they can see the folder path up to ....\m000155b1.mod in the DOORS DB data area. If they can't see it, then something has gone wildly wrong as it looks as though that module has been deleted and purged but the DOORS Explorer still has an index entry pointing to the module.

If they find the missing tree.dtc file in the back-ups, it would probably be a good idea to create a new DOORS data directory somewhere else and do a full DB restore from the backup under that, then set up a new DOORS DB server instance to point to that data and check if the module your after is OK (refer to the "Managing Telelogic DOORS" manual). If OK, then just exactly how you restore this back into the production DB will depend on many what you're comfortable with - if the back-up is more than a day old, then doing a full restore will blow away all changes to other modules since that backup date. You can try to just surgically restore all files under the ....\m000155b1.mod folder but only after you have taken a full back-up of the DOORS data area just in case this doesn't work (this is risky - all other modules linking to this module would need to be checked). Or, take an archive of the module in the restored DB instance and restore it back into the production DB - but you will need to replicate incoming\outgoing links manually, or if you know how to implement the "link by attribute" method, this would work as well. I just hope there are no residual link issues with other modules that were originally linking with this one.

Paul Miller

Re: DOORS Error when opening Module
SystemAdmin - Mon Aug 16 17:59:43 EDT 2010

Not sure if this is a coincidence or you raised a problem report with IBM, but overnight IBM released a Technote that covers exactly the problem you are experiencing and provides a possible solution.

Let us know how you go with this.

Paul Miller
Attachments

attachment_14511231_IBMTechNote-DOORS-UnableToOpenModuleErro.pdf

Re: DOORS Error when opening Module
Stocks - Tue Aug 31 10:38:05 EDT 2010

Hello,
I also get this error. If I edit a module that was migrated from ver7 using web access I get the above error next time I go into the module. So far I have broken 4 different modules with this problem. The fix here is the same fix that IBM support gave, and it works, but I am still able to break all the other modules. Still awaiting conclusion from support.

Re: DOORS Error when opening Module
vppatel - Tue Aug 31 13:52:12 EDT 2010

SystemAdmin - Mon Aug 16 17:59:43 EDT 2010
Not sure if this is a coincidence or you raised a problem report with IBM, but overnight IBM released a Technote that covers exactly the problem you are experiencing and provides a possible solution.

Let us know how you go with this.

Paul Miller

We raised a problem report with IBM, and they were quick to respond. The Technote is exactly what we did to resolve the problem.

Regards

Re: DOORS Error when opening Module
SystemAdmin - Tue Oct 05 13:02:43 EDT 2010

Stocks - Tue Aug 31 10:38:05 EDT 2010
Hello,
I also get this error. If I edit a module that was migrated from ver7 using web access I get the above error next time I go into the module. So far I have broken 4 different modules with this problem. The fix here is the same fix that IBM support gave, and it works, but I am still able to break all the other modules. Still awaiting conclusion from support.

I had to test this myself also, and sure enough the very first attempt to edit a module created with DOORS 7.x stalled in DWA with error "An error occurred while attempting to edit the value", and afterwards I could not cancel the save or close the module. And when trying to open the module in read-only with another DWA session gave me "node_not_found" error and with Client the same "No such file or directory ../treedata.dtc" error as described in this discussion.

What troubles me is when this will be solved, is it fixed in DWA 1.4 already? And the workaround suggests restarting server after file replace, which is not something we could do during office hours. We have actually done several replacements like this with server running, and do not seem to have experienced any problems with that.

Re: DOORS Error when opening Module
John.Pullman - Fri Oct 22 06:46:13 EDT 2010

vppatel wrote:
We raised a problem report with IBM, and they were quick to respond. The Technote is exactly what we did to resolve the problem.

Regards

Where can I find the related documentation? I'm a beginner, Could you explain it more clearly?
You mean you got the way to solve the problem?

Re: DOORS Error when opening Module
vppatel - Thu Oct 28 10:11:54 EDT 2010

John.Pullman - Fri Oct 22 06:46:13 EDT 2010

vppatel wrote:
We raised a problem report with IBM, and they were quick to respond. The Technote is exactly what we did to resolve the problem.

Regards

Where can I find the related documentation? I'm a beginner, Could you explain it more clearly?
You mean you got the way to solve the problem?

Look up 4 posts and you will see that Paul Miller attached the technote.