Troubleshooting
Problem
The IBM Rational DOORS 9.5.0.1, 9.5.1, and 9.5.1.1 clients can crash when viewing objects if the DOORS module contains an RTF table with non-Unicode symbols.
Symptom
When viewing an object in an IBM Rational DOORS module, the DOORS client will crash with a diagnostic log and also a DXL error that looks similar to this:
doors.exe caused an EXCEPTION_ACCESS_VIOLATION in module MSVCR80.dll at 0023:732B55A8, get_amblksiz()+0360 byte(s)
Cause
This issue has been identified as a product defect and logged under APAR PM88716.
Environment
This has been seen with IBM Rational DOORS client versions 9.5.0.1, 9.5.1, and 9.5.1.1, when viewing modules that contain RTF tables with non-Unicode symbols.
Diagnosing The Problem
The easiest way to determine whether you are having this problem is to open the problem module with an IBM Rational DOORS client older than 9.5.0.1 and see whether the crash is reproducible with this version. If it is not, you can inspect the object that makes DOORS crash and the objects around it. Look for an RTF table with non-Unicode symbols in it.
If you are not sure if it is an RTF table:
Generally, RTF tables are OLE objects and they have black borders. However, for this issue, the thing to look for is non-Unicode symbols in a table. RTF tables without non-Unicode symbols will not cause a crash.
Resolving The Problem
APAR PM88716 is resolved in IBM Rational DOORS 9.5.1.2. It is a client-side fix, so you can take advantage of the fix by upgrading your DOORS client to 9.5.1.2.
If you cannot upgrade to DOORS 9.5.1.2 immediately, you can use the following workaround:
- Change the format of the data so an RTF table is not used.
- Remove the non-Unicode symbols from the RTF table.
Was this topic helpful?
Document Information
Modified date:
01 May 2020
UID
swg21648643