![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Error while parsing node data Topic Summary: What can I do when I receive this error messsage: "Error while parsing node data" Created On: 17-Oct-2007 18:53 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: I will reply and answer myself, since I find an answer into a previous question. We must say OK as many as time it is necessary (225 times in my case) to open the module. The corruption is due to an ennumarative attribute type which have been changed without being properly saved (how this could happen ? ). 225 object were affected by the attribute value change. While in the module I rechanged the ennumarative attribute type and save the module. I quitted the module and Doors and every thing worked. Marc-Alain Simard | |
![]() |
|
Each time we try to acces a module we get this message "Error while parsing node data". We can not get rid of the message, each time we have use task manager to kill the DOOORS process.
Where this come from? What can we do? Marc-Alain Simard Requirement Engineer CAE Montreal, Canada |
|
![]() |
|
![]() |
|
I will reply and answer myself, since I find an answer into a previous question.
We must say OK as many as time it is necessary (225 times in my case) to open the module. The corruption is due to an ennumarative attribute type which have been changed without being properly saved (how this could happen ? ). 225 object were affected by the attribute value change. While in the module I rechanged the ennumarative attribute type and save the module. I quitted the module and Doors and every thing worked. Marc-Alain Simard |
|
![]() |
|
![]() |
|
Did you say you changed some enumerations in the Type, then changed object attribute values that used the new enumerations, and the obj-attr values were saved but the changes to the enumerations where not? So when the module opened the objects had values that were illegal?
Tried to simulate that: open exclusive edit an attribute, switch to Shared, lock a section, change an object-value, close and save the section, switch back to exclusive, close the module without saving. Didn't work, the module gets closed and you are prompted to 'save' when switching from Exclusive to Shared. Or perhaps you modified obj-attr values, changed enumerations, then used History to revert back to the old values? Or perhaps all the objects were Partitioned out, you modified Enumerations, then restored the partion which had the illegal values in it? Or perhaps someone was playing Fizbin on a Tuesday? - Louie |
|
![]() |
|
![]() |
|
Are you still using DOORS 7.0? If I remember correctly, 7.0 had a bug like this.
------------------------- Pekka.Makinen@softqa.fi SoftQA Oy -http://www.softqa.fi/ |
|
![]() |
Telelogic DOORS
» Administration
»
Error while parsing node data
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.