Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: DOORS error while opening a module
Topic Summary: Error while parsing file
Created On: 11-Nov-2004 15:49
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 11-Nov-2004 15:49
User is offline View Users Profile Print this message


Ananda Badugu

Posts: 20
Joined: 3-Feb-2003

Hi


I'm getting an error while opening formule module in DOORS 6.0SR1. Please help me to resolved this problem. see below the error message that got.

"Error while parsing file '/vsdata/40/70/m00007a41.mod/current.ver/treedata.dt' at line 26648: expecting string"



Thanks in Advance.



Ananda

Report this to a Moderator Report this to a Moderator
 11-Nov-2004 16:34
User is offline View Users Profile Print this message


Mandy Livingstone

Posts: 15
Joined: 21-Jan-2003

You should contact your local customer support department with this - all data integrity issues should be reported to customer support

Regards

Mandy
Report this to a Moderator Report this to a Moderator
 9-Mar-2006 19:00
User is offline View Users Profile Print this message


Craig Forant

Posts: 56
Joined: 21-Feb-2005

Did you ever get a resolution to this?

I am curious because I am having similar problems.

Craig
craigf@softcomputer.com

-------------------------
Craig Forant
me@craigforant.com
Report this to a Moderator Report this to a Moderator
 10-Mar-2006 08:18
User is offline View Users Profile Print this message


Hubertus Grobbel

Posts: 58
Joined: 3-May-2005

Hi Craig,

the error message is indeed strange.

My experienced errors during load of a module are:
- trigger enabled with code that was doing something unexpected-> disable triggers
- DXL-Attributes, which were refreshed and lead to strange behaviour-> review code of DXL-Attributes

Maybe this helps... :-)

Regards
Hubertus

Edited: 10-Mar-2006 at 08:19 by Hubertus Grobbel
Report this to a Moderator Report this to a Moderator
 10-Mar-2006 18:02
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

That's a database corruption error; not something that can be created nor fixed with DXL
Report this to a Moderator Report this to a Moderator
 10-Mar-2006 18:09
User is offline View Users Profile Print this message


Craig Forant

Posts: 56
Joined: 21-Feb-2005

Any ideas on where to start to fix it?

-------------------------
Craig Forant
me@craigforant.com
Report this to a Moderator Report this to a Moderator
 10-Mar-2006 18:11
User is offline View Users Profile Print this message


Craig Forant

Posts: 56
Joined: 21-Feb-2005

It happens during an HTML Export, which enumerates links through several modules and projects. It is hard to tell where this message is coming from.

-------------------------
Craig Forant
me@craigforant.com
Report this to a Moderator Report this to a Moderator
 12-Mar-2006 14:36
User is offline View Users Profile Print this message


Eric Piallat

Posts: 33
Joined: 26-Jan-2004

You may check if the faulty module (#00007a41) is the exported one, or one of the linked module.



-------------------------
E. Piallat
CeBeNetwork
Report this to a Moderator Report this to a Moderator
 14-Mar-2006 16:36
User is offline View Users Profile Print this message


Craig Forant

Posts: 56
Joined: 21-Feb-2005

how do I determine the Module number/code? Is there a DXL Script I can run?

-------------------------
Craig Forant
me@craigforant.com
Report this to a Moderator Report this to a Moderator
 15-Mar-2006 01:23
User is offline View Users Profile Print this message


Paul Ransley

Posts: 10
Joined: 20-Sep-2004

Guess this should be in the DXL forum but here goes. Use uniqueID, as it says in the manual;

Declaration

string uniqueID({Item i|Folder f|Project p|ModName_ 
modRef})

Operation

Returns as a string a unique ID for the item specified


If you have a module open run the following in the DXL editor;

string tempID = uniqueID(module(fullName(current Module)))
print tempID


The attached code is an old script I had to hand that runs through the database listing all modules (formal or link) and collects module information including uniqueID. So if you've got a message giving the ID but dont known the module, run the script, and search through the output to find the module code number the error is giving you, that will at least tell the project\module name.

Have you raised the error your getting with Telelogic Support before you start trying to fix?

-------------------------
Paul Ransley<BR><BR>Beaver Computer Consultants Limited

Edited: 15-Mar-2006 at 01:47 by Paul Ransley
Report this to a Moderator Report this to a Moderator
 4-Jan-2007 17:58
User is offline View Users Profile Print this message


Chris Jones

Posts: 177
Joined: 1-Jul-2005

Just to simplify things a little bit---if you have a Unique ID (from an error message or whathaveyou) and want to find out what it belongs to....

There's a DXL function Item itemFromID (string) that will do it for you. See the attached.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.