DXL errors when running DOORS reports from RPE


When you try to run a document generation either from the “Publish” menu in DOORS or from RPE stand alone you get a DXL error like the one bellow:

-E- DXL: <C:\Program Files\IBM\Rational\Publishing Engine\1.1.1.2\source\DOORS\dxl\doors driver\getDOORSVersion.dxl:3> could not open include file (source/DOORS/dxl/doors driver/getDOORSVersion.inc) (No such file or directory)
Included from:
<Line:1>

But getDOORSVersion.inc exists so what is wrong? The answer is in how RPE 1.1.1.2 and newer versions refer the inc files needed for DOORS data extraction. With RPE 1.1.1.2, the inc files are no longer referred to with absolute paths. The changes were needed in order to cope with the new DXL security mechanisms in DOORS 9.3.

And the error actually hints this, as it states that <source/DOORS/dxl/doors driver/getDOORSVersion.inc> is not found and not <C:\Program Files\IBM\Rational\ Publishing Engine\1.1.1.2\source/DOORS\dxl\doors driver\getDOORSVersion.inc> or some other absolute path.  See also the content of getDOORSVersion.dxl

#include <source/DOORS/dxl/doors driver/getDOORSVersion.inc>

So how does it work in RPE 1.1.1.2 and newer? The full path is built by the DOORS DXL interpreter by using the relative path and the “base folder” specified in the addins property. This property can be set from command line or in the registry in HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\9.X\Config
In some installations the key HKEY_CURRENT_USER\Software\Telelogic\DOORS\9.X\Config also exists and will overwrite whatever is set in HKLM.

NOTE: the command line entry will override whatever values are set in the registry.

So how do I fix this? There are actually several solutions you can use.

Add the path to the RPE installation in the DOORS registry keys

For RPE’s DXLs to work the path to RPE_HOME must be present in these registry entries. The RPE installer adds the path to the HLKM key but if you have a customized DOORS installation you need to manually add the entry or update the custom installer to do it.

Start DOORS with the <addins> command line switch

If none of the entries exist and you do no want/cannot create them you can specify the addins path as a command line option when starting DOORS. Read more on  DOORS command line switches.

You could use a command line like the one bellow to start DOORS:

"C:\Program Files\IBM\Rational\DOORS 9.3\bin\doors.exe" -data 36677@giediprime -addins "C:\Program Files\IBM\Rational\Publishing Engine\1.1.1.2"

NOTE: if the path to the addins folder contains spaces make sure you enclose it in quotes.

Copy the RPE  DXLs in a folder already “known” to DOORS

If you already use the <addins> command line switch and don’t want yet another folder added to it, you can copy the entire “source” folder from RPE’s installation into the folder specified by the addins switch. For example, if your start DOORS with the command bellow you  would have to copy the source folder in the Z:\DOORS\SharedAddins folder

"C:\Program Files\IBM\Rational\DOORS 9.3\bin\doors.exe" -data 36677@giediprime -addins "Z:\DOORS\SharedAddins"
Location of the source folder


About these ads

2 thoughts on “DXL errors when running DOORS reports from RPE”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s