![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DOORS: Error while parsing data Topic Summary: DOORS: Error while parsing data Created On: 13-May-2005 20:27 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Is it just Error while parsing data or is it Error while parsing node data? If it is the latter, then it is a bug somehow related to changing the value of an attribute of type enumerated while in Shareable Edit mode when using the 7.0 client. If I remember correctly, a prerequisite was that you first modified the attribute definition by adding one or more new enum values. It will give you one error for each changed attribute value, so the 50 times you mention is related to you having 50 such changes in your module. When we had those problems we used the history to restore the attribute values to the pre-problem state. This worked great in our case as it was only one module and the problem was discovered almost immediately. Best regards Niclas | |
![]() |
|
We have this issue with one of our modules. Support is saying that this is caused by corruption but cannot specifically say what is the reason.
We have DOORS 7.0 SP1 server with mix 7.0 SP1 and 7.1 clients. Upgrading our database might take sometime but I'm hoping to solve this issue in our current environment. Two recovery procedures have been done and the separate procedure seemed to work for a while, the problem went away. With our disgust, after a few weeks the problem comes back. The error "DOORS" Error while parsing data" appears about 50 times before the module is finally open. When the module is open, everything seems to be okay but we are worried that one day everything will just stop working. The module is configured to have 2nd level shareable edit sections. The recovery procedures done were: - Archive the whole project containing the module. Rename the old. Recover the Archived copy. - Second time was archive the module, export it to 7.1 database, run integrity checker, did not find anything, then return the "checked" module (after renaming the old), recreate all permissions and links. These distinct individual procedures seemed to fix the problem for a couple of weeks, then the error just come back. Any idea why this is happening? Possible resolution is greatly appreciated. Thank you. Jetzu Baay |
|
![]() |
|
![]() |
|
Is it just Error while parsing data or is it Error while parsing node data? If it is the latter, then it is a bug somehow related to changing the value of an attribute of type enumerated while in Shareable Edit mode when using the 7.0 client. If I remember correctly, a prerequisite was that you first modified the attribute definition by adding one or more new enum values. It will give you one error for each changed attribute value, so the 50 times you mention is related to you having 50 such changes in your module.
When we had those problems we used the history to restore the attribute values to the pre-problem state. This worked great in our case as it was only one module and the problem was discovered almost immediately. Best regards Niclas |
|
![]() |
|
![]() |
|
Niclas,
Thanks for the reply. The error is actually, "Error while parsing node data". Similar to what you had experienced. We will try to apply the corrections you suggested and will inform you of the result. Jetzu Baay |
|
![]() |
|
![]() |
|
Niclas,
The clients who are having this issue are using the basic 7.0 SP1 version. No patch. Do you know if the problem is fixable using patches for the same version? We have 3 patches for 7.0 SP1. Do you have to go to version 7.1 to avoid having the issue reappear? Thank you. Jetzu Baay |
|
![]() |
|
![]() |
|
I am sorry but I have rather vague memories of this. I checked the Case Tracking on this site and saw that I logged this issue on January 28, 2004. At that time we upgraded from 7.0 to 7.0 SP1 patch 18449 and that was the last we saw of the problem.
|
|
![]() |
|
![]() |
|
Niclas,
We are now okay. We restored the module and updated our clients to 7.1. Thank you very much for your help! Jetzu Baay ![]() Edited: 25-May-2005 at 13:55 by Ramon Jetzu Baay |
|
![]() |
|
![]() |
|
I have a similar issue to this thread...
I get the message "error while parsing node data" about 15-20 times. then a message "error while parsing file '/v6data/80/00/m00000d89.mod/current.ver/treedata.dt' at line 1307553: expecting DocumentVersion This happens several times during an HTML Export. The difference from the above solutions is that I believe all my clients are on DOORS 7.1-Patch 12. Any help or insight would be appreciated. Craig ------------------------- Craig Forant me@craigforant.com |
|
![]() |
|
![]() |
|
I just experienced this problem in DOORS 8.2 after changing a multi-valued enumerated attribute to a single value. I had changed several modules but only one was reporting "error while parsing node data".
I resolved it, after reading this article, by reverting the attribute back to multi-value, saving the module then setting it back to a single value again and re-saving the module. I did this as Administrator but suspect any user with exclusive edit rights could have done the same. Hope this helps. - Martin ------------------------- - Martin |
|
![]() |
Telelogic DOORS
» Administration
»
DOORS: Error while parsing data
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.