PM64241: Exception_Access_Violation error when switching Edit Modes in DOORS
A fix is available
Closed as program error.
Exception_Access_Violation error when switching Edit Modes in DOORS (from Exclusive Edit to either Read Only Mode or Shareable Edit Mode) by following these steps: Versions: reported in DOORS Client 188.8.131.52, we are able to reproduce even with 184.108.40.206 Steps to reproduce: ============== 1.? Open any Module and create new Attribute (while ensuring that the option 'Add new attribute to current view' is enabled) You can also create new Attributes by choosing any existing Attributes (provided that the original Attribute has the option 'Add new attribute to current view' enabled themselves) 2.? Repeat step # 1 atleast 3 times, so that there are 3 new columns added to the View in the Module. 3.? Goto Edit ? Edit Mode and select either Read Only Mode OR Shareable Edit Mode. 4.? Choose 'No' when prompted to save unsaved changes in the Module. We would observe the Exception Access Violation error message as follows: ===================================== -R-E- DXL: ?config/menuFns.inc:391? An unexpected error has occurred: doors.exe caused an EXCEPTION_ACCESS_VIOLATION in module doors.exe at 0023:00402F31 -R-F- DXL: ?config/menuFns.inc:391? internal error, please submit a bug report ===================================== Along with a diagnostic log file as attached to this record.
DOORS shows an assert message when switching access modes with unsaved changes.
Unable to reproduce in newer versions of DOORS (9.4 onward)
There is no workaround for this issue
This happens in versions of DOORS prior to DOORS 220.127.116.11
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels