DOORS crashes while trying to access object properties

We are using DOORS 9.4.0.0. In one of the modules, we are trying to access the object properties. The problem is that for 2 specific objects, as soon as we try to access the properties, the DOORS goes into non responsive state and if we try to kill the module, the whole DOORS crashes.

There isn't anything unusual about these two requirements. Both these requirements have incoming links. But other objects which have in-links, shows properties window. One object contains text and a table in the child object under it.

The very next object has a big picture in it. Is there a way to fix this. Following is the crash info we got:
=========================================
Problem Event Name: APPCRASH
Application Name: doors.exe
Application Version: 9.4.0.0
Application Timestamp: 5074302a
Fault Module Name: MSFTEDIT.DLL
Fault Module Version: 5.41.21.2510
Fault Module Timestamp: 4ce7b8f2
Exception Code: c0000005
Exception Offset: 00001a30
OS Version: 6.1.7601.2.1.0.18.10
Locale ID: 1033
Additional Information 1: ccc2
Additional Information 2: ccc26e050958f1c9740725e357b088e2
Additional Information 3: 0007
Additional Information 4: 00071c3975905dfdac47529874e90543
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
SystemAdmin - Wed Feb 27 06:19:50 EST 2013

Re: DOORS crashes while trying to access object properties
SystemAdmin - Wed Feb 27 06:26:39 EST 2013

While accessing properties of other requirements in the same module, we get the following DXL error:

-R-E- DXL: <Line:12> unknown Object attribute (A2gila)
-I- DXL: execution halted

This attribute does not exist in the module currently. Also, there aren't any triggers on the module.

Re: DOORS crashes while trying to access object properties
SystemAdmin - Wed Feb 27 06:30:01 EST 2013

While accessing properties of other requirements in the same module, we get the following DXL error:

-R-E- DXL: <Line:12> unknown Object attribute (A2gila)
-I- DXL: execution halted

This attribute does not exist in the module currently. Also, there aren't any triggers on the module.

Re: DOORS crashes while trying to access object properties
SystemAdmin - Wed Feb 27 06:34:38 EST 2013

SystemAdmin - Wed Feb 27 06:30:01 EST 2013
While accessing properties of other requirements in the same module, we get the following DXL error:

-R-E- DXL: <Line:12> unknown Object attribute (A2gila)
-I- DXL: execution halted

This attribute does not exist in the module currently. Also, there aren't any triggers on the module.

If there are no module triggers, perhaps there are database, project, object or attribute triggers? Any DXL attribute, any DXL layout column?

As "A2gila" is an attribute which seems to be specific to your data model, I would say that the script which runs also stems from your company.
HTH
Mike

Re: DOORS crashes while trying to access object properties
llandale - Wed Feb 27 15:54:46 EST 2013

If you kill the module you will kill DOORS and of course get some unpleasant error message. That dump is not interesting.

We have some modules where the object properties takes about 10 minutes the first time. You should try to wait it out and see if it comes back eventually.

As for your 2nd problem, pretty obviously you have some old attr-DXL running which references that attribute, because the Object Properties tries to display all the attribute values. Run the following, then look for that named attribute:

AttrDef ad string Name 

for ad in (current Module) 

do 
{  

if (ad.dxl) then 
{  Name = ad.name print 
"=== Attribute: " Name 
" ===\n" (string ad.dxl) 
"\n" 
} 
}

-Louie

Re: DOORS crashes while trying to access object properties
SystemAdmin - Thu Feb 28 10:12:12 EST 2013

llandale - Wed Feb 27 15:54:46 EST 2013
If you kill the module you will kill DOORS and of course get some unpleasant error message. That dump is not interesting.

We have some modules where the object properties takes about 10 minutes the first time. You should try to wait it out and see if it comes back eventually.

As for your 2nd problem, pretty obviously you have some old attr-DXL running which references that attribute, because the Object Properties tries to display all the attribute values. Run the following, then look for that named attribute:


AttrDef ad string Name 

for ad in (current Module) 

do 
{  

if (ad.dxl) then 
{  Name = ad.name print 
"=== Attribute: " Name 
" ===\n" (string ad.dxl) 
"\n" 
} 
}

-Louie

Thank you louie for the script.

I got the following output:

=== Attribute: IN-LINKS-AGILA ===
// DXL Do display Object Text for IN link.dxl

Can't disclose further as it is confidential.

Couldn't locate this attribute in the module. Do you think recreating this attribute would help?

Re: DOORS crashes while trying to access object properties
kbmurphy - Thu Feb 28 11:32:44 EST 2013

SystemAdmin - Thu Feb 28 10:12:12 EST 2013
Thank you louie for the script.

I got the following output:

=== Attribute: IN-LINKS-AGILA ===
// DXL Do display Object Text for IN link.dxl

Can't disclose further as it is confidential.

Couldn't locate this attribute in the module. Do you think recreating this attribute would help?

I would contact your DOORS Administrator or sign in with the Administrator account yourself. I wanted to think this was an access rights issue but if you ran that DXL and it said that the attribute was there, then you should be able to see the Attribute in the GUI. You should be able to insert a column with that attribute in it.

Also, you have more attribute DXL than that, and even though you were able to narrow this down with a DXL error, the other attr DXL could still be causing issues too.

Re: DOORS crashes while trying to access object properties
SystemAdmin - Tue Mar 05 06:52:04 EST 2013

kbmurphy - Thu Feb 28 11:32:44 EST 2013
I would contact your DOORS Administrator or sign in with the Administrator account yourself. I wanted to think this was an access rights issue but if you ran that DXL and it said that the attribute was there, then you should be able to see the Attribute in the GUI. You should be able to insert a column with that attribute in it.

Also, you have more attribute DXL than that, and even though you were able to narrow this down with a DXL error, the other attr DXL could still be causing issues too.

Thank you all for your suggestions and pointers. We found that there were some old DXL attribute which were causing this. Deleting them fixed the issue.

Thank you..