![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
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 |
![]() |
![]()
|
![]() |
|
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. |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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.
|
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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?
|
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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.
|
|
![]() |
Telelogic DOORS
» General Discussion
»
EXCEPTION_ACCESS_VIOLATION
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.