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: EXCEPTION_ACCESS_VIOLATION
Topic Summary: DOORS will exit now.
Created On: 6-Aug-2007 14:41
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.
 6-Aug-2007 14:41
User is offline View Users Profile Print this message


Corey Carroll

Posts: 48
Joined: 25-May-2006

DOORS has been crashing and spitting out errors quite a bit lately.  I had the network admin reboot the DOORS server last week and asked them to monitor the performance of the server.  Unfortunately DOORS shares a server with System Architect and a few other programs.

One error I cannot decipher is the EXCEPTION_ACCESS_VIOLATION error.  The Diagnostic Log shows that 75% memory was in use and a bunch of other worthless infomation.  The error window says, "DOORS has encountered an error from which it cannot recover.  DOORS will exit now."  The user has been trying to modify attributes in a view with a few other attributes and a filter.  Nothing else fancy is going on.  The network admin says that there have been no memory peaks on the server and it is runnign well.  Any ideas on how to fix this?

We are running version 7.1 via Citrix and client applications.

Report this to a Moderator Report this to a Moderator
 6-Aug-2007 15:50
User is offline View Users Profile Print this message


Peter Albert

Posts: 232
Joined: 30-Dec-2005

I never ran into such an error when "just" modifying DOORS module through the DOORS GUI. However, it happens (quite often) when I am developing new DXL scripts. An error message like this shows up when e.g. the DXL scripts tries to access a buffer variable after it has been deleted, or a skip list entry is assigned with the wrong variable type etc. I would therefore guess, that, although you say that "nothing else fancy is going on", there might be some DXL going on, either in a layout DXL column, as attribute DXL, or even a trigger. It might be worth checking that option, and, if you find some DXL, carefully check that the script behaves well.

Cheers,

Peter
Report this to a Moderator Report this to a Moderator
 7-Aug-2007 00:15
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

This sort of error is almost always a client problem, so looking to resolve it on the server or by restarting the DOORS service is almost always a waste of time ..err.. a bad waste of time.

Peter is correct, its probably a DXL problem.

My guess is you have some layout or attr DXL the performs some sort of filter or sort inside it (that's a big no-no), or that the attribute value you are changing will result in a changing the filtered state of the object you are changing; such as filtering for objects that contain 'shall' but then removing 'shall' from an object. Also perhaps, even though we don't use shared mode here, perhaps there is an issue with locked shared sections combining poorly with some sort of ..err.. some kind of sort.

- Louie
Report this to a Moderator Report this to a Moderator
 7-Aug-2007 15:51
User is offline View Users Profile Print this message


Corey Carroll

Posts: 48
Joined: 25-May-2006

I was finally able to replicate this error.  I opened the module in shareable edit, and accessed the view they were using.  I was able to edit, save, edit save, and so forth for quite some time.  I tried exporting the entire module with multiple attributes to Word.  It exported slowly, but it exported.  I closed the module, walked away.  Upon re-opening the module in shareable edit, I tried to access the view and DOORS blew up on me.  It gave the exception access violation error and shut down.  I will check the DXL attributes that are used in that view.  However, it also occured for the other user in standard view with one additional text attribute that only contains one letter per object.
Report this to a Moderator Report this to a Moderator
 7-Aug-2007 23:53
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I assume when you 'edit and save' you mean 'lock section, edit and save'.

Is it perhaps an issue when more than one person has it open Shared at the same time? Is it possible that when the sections are setup that some object's rights now prevent someone from even seeing THAT object, even though they can see lower-level objects? If so, I wonder what happens when that someone tries to lock that section; DOORS probably doesn't know where the section really is.

Put the attached in a column and save the view; it displays the specific access rights, which are the objects defined as 'sections'. Look for objects that prevent some folks from even R reading the object.

- Louie
Report this to a Moderator Report this to a Moderator
 8-Aug-2007 15:47
User is offline View Users Profile Print this message


Corey Carroll

Posts: 48
Joined: 25-May-2006

I ran the script and all the sections had the exact same access rights.  One of the users said DOORS has crashed 4 times on him this morning.  He is trying to move objects around to different sections, and is in shareable edit.  Does this cause adverse affects in DOORS?
Report this to a Moderator Report this to a Moderator
 8-Aug-2007 16:16
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Moving objects around is real tricky in Shared mode, you need to have all affected sections locked. Forget that, just use Exclusive mode to do module-level changes like creating attributes and restructuring the objects.

I don't know why you'd get DXL error doing that, however; you probably have some other problem. Check out the Attr DXL and Layout DXL and possibly any triggers in the module.

- Louie
Report this to a Moderator Report this to a Moderator
 8-Aug-2007 16:42
User is offline View Users Profile Print this message


Corey Carroll

Posts: 48
Joined: 25-May-2006

I had one user try to perform his work in Exclusive edit....he had another crash. It appears that the errors are occuring when they are saving the module. The system crashes before DOORS saves any of the changed information. Also, I am not getting a DXL error on this issue....but I am on another issue concerning a different module. This error just says unrecoverable error, DOORS will exit.
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.