When RPE Launcher/Studio load and run DOORS templates one of the first actions performed is to read the path of the DOORS executable on the current machine. That action is required to populate this value when creating a new docspec or to validate that the value stored in the document specification is correct.
RPE finds this information by reading registry values, specifically HKLM\SOFTWARE\Telelogic\DOORS\9.x\InstallationDirectory and HKLM\SOFTWARE\Telelogic\DOORS\9.x\Config\Data. This works well for all DOORS 32 bit versions but not for the 64 bit ones. This failure is perceived as a slowness of RPE to load docspecs: RPE 220.127.116.11 Launcher slow loading Specifications
NOTE: the document generation is not affected by this problem, this behavior is limited exclusively to loading and configuring a docspec.
The problem is caused by how the Windows registry is accessed by 32 and 64 bit applications. The Windows Registry Redirector ensures that by default 32 bit processes like RPE see the 32 view of the registry and not the 64 bit one. This means that RPE will not see the registry entries created by a 64 bit application liked DOORS 9.6 64 bit.
RPE will be enhance to be able to access both the 32 and the 64 bit views of the registry but in the meantime there are 2 solutions to the problem:
- Define the DOORS location through RPE flags – this is the preferred approach and should be used even for the 32 bit version of DOORS where this issue does not occur.
- Define the 32 bit registry keys RPE is looking for:
- create the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Telelogic\DOORS\9.6 key
- under the 9.6 key create a string value called InstallationDirectory and copy the value from HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\9.6
- create the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Telelogic\DOORS\9.6\Config key
- under the Config key create a string value named Data and copy the Data value from HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\9.6\Config