Fixing DXL errors when running Rational DOORS reports

When you try to generate a document from either the Publish menu in IBM® Rational® DOORS® or the IBM Rational Publishing Engine Launcher, you receive a DXL error.

About this task

Error examples:
  • E- DXL: <Line3>could not open include file (source/DOORS/dxl/schema discovery/const.inc) (No such file or directory).
  • E- DXL: <RPE_HOME\source\DOORS\dxl\doors driver\getDOORSVersion.dxl:>could not open include file (source/DOORS/dxl/doors driver/getDOORSVersion.inc) (No such file or directory).
This issue is caused by how Rational Publishing Engine refers to the getDOORSVersion.inc files needed for the Rational DOORS data extraction. In Rational Publishing Engine, the .inc files are referred to with relative paths instead of absolute paths. If Rational DOORS is already installed when you install Rational Publishing Engine, Rational Publishing Engine creates an the add-ins registry so that Rational DOORS can resolve those relative paths. If Rational Publishing Engine installed before Rational DOORS, this registry cannot be created, which often results in DXL errors. If the error was caused for this reason, you can reinstall the Rational Publishing Engine add-ins.

The path that is specified in the add-ins registry includes a full path, which is built by the Rational DOORS DXL interpreter with the relative path provided by Rational Publishing Engine and with the "base" folder specified in the addins property of your Rational DOORS installation. Example: HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\9.X\Config. If you installed the products in the correct order, it is also possible that a command-line entry overwrote the value set in this registry. For example, the key HKEY_CURRENT_USER\Software\Telelogic\DOORS\9.X\Config also was also created and had overwritten the value set in HKEY_LOCAL_MACHINE registry key. If the error was caused for this reason, you can specify the add-ins path as a command-line option when starting Rational DOORS.

Procedure

Select one of these workarounds:


Feedback