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: null Link Module Descriptor DXL error
Topic Summary:
Created On: 12-Jan-2004 11:12
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.
Answer This question was answered by , on Tuesday, January 13, 2004 12:40 PM

Answer:
Paul,

Some possibilities:

1. There is a module default view for that user that is not the "Standard view" and that includes layout or attribute DXL columns. The user can check this by doing a "View->Manage Views..." from the module pulldown menu.

2. There is a "module open" DXL trigger generating the error. The user can temporarily disable triggers by starting DOORS with the
"-notriggers" command line option. Note that the user must have the "manage database" power to disable triggers during a DOORS session.

3. The DXL "for LinkModuleDescriptor in Folder" loop is failing because the user doesn't have access to "something". I'm not sure what the "something" would be. He apparently has read access to the module and to the containing folder/project. Are there any links that others see in the module, but this user does not?
 12-Jan-2004 11:12
User is offline View Users Profile Print this message


Paul Worrall

Posts: 87
Joined: 30-Sep-2003

One of our users gets the following DXL error when opening one particular formal module:

-R-E - DXL: <Line:2> null Link Module Descriptor do loop parameter was passed
-I- DXL: <Line:3> execution halted

The default view of the module is 'Standard view' so no Attribute or Layout DXL should be invoked.
The user does not get the error message with other modules, and other users (with different access rights) do not get the error message with any modules. Once opened, the module appears to show all the correct information.

Can anyone suggest a possible cause of this effect, or a line of investigation I should pursue?

Regards.
Report this to a Moderator Report this to a Moderator
 13-Jan-2004 12:44
User is offline View Users Profile Print this message


Paul Worrall

Posts: 87
Joined: 30-Sep-2003

Thanks Roger,
I found a trigger in the project which, when removed, solved the problem. I hope it wasn't doing anything important!
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.