Unable to open word-break file specified with -ttwrdrul startup parameter


Article Number000036168
EnvironmentProduct: Progress
Version: 9.1x
Product: OpenEdge
Version: 10.x, 11.x
OS: Windows
Question/Problem Description
A user running a local OpenEdge client connected to a remote database is unable to open the word-break file (proword.n) specified with the -ttwrdrul startup parameter. Error 2736 is raised.
Steps to Reproduce
Clarifying Information
Full OpenEdge client is installed locally.
Not installed with NetSetup.
Not a WebClient installation.
Application is started with an .ini file.
PROWRDn environment variable is not set.
proword.n file exists in client DLC.
The user experiencing the problem has full operating system privileges on proword.n.Conn
Database is on a remote server.
proword.n does not exist in the database directory.
Other users do not have the problem, even when logged in on the affected user's computer.
The affected user does not have the problem when logged in on other computers.
When proword.n is copied to the DLC of the database server, the problem does not occur.
Error MessageUnable to open word-break table file <table-num>. (2736)
Defect/Enhancement Number
When a word-break file is specified for use with temp-tables by the -ttwrdrul client startup parameter, OpenEdge searches the Windows registry for the directory in which to look for proword.n. This is true even if an .ini file is being used.

OpenEdge first looks for the key:
If it is found, it looks for 
where "n" is the number of the word-break file;
for example PROWD2 would specify the location of proword.2 

If PROWDn is not set, OpenEdge looks for 

If OpenEdge does not find HKEY_CURRENT_USER\Software\PSC\Progress\<version>\Startup at all, it repeats the same sequence in:

If it does not find an appropriate key, it looks for prowd.n in the Database Server's DLC.

In this case, the affected user had keys specified in:
but the DLC key was not specified.
OpenEdge therefore did not look in:
HKEY_LOCAL_MACHINE because it had already found HKEY_CURRENT_USER.
Instead, it defaulted to look in the database server's DLC for proword.n.
But proword.n did not exist in the database server's DLC, error 2736 was raised.

When other users logged in using the affected user's machine, they did not have the key:
Instead, OpenEdge looked in HKEY_LOCAL_MACHINE and found the correct DLC.

Similarly, when the affected user logged into other machines they did not have the key:
Instead OpenEdge looked in HKEY_LOCAL_MACHINE and found the correct DLC.
For the affected user add a DLC key to:
Add  a new "String Value" on the key: HKEY_CURRENT_USER\Software\PSC\PROGRESS\<version>\Startup
By Right-mouse clicking on the Right-hand-pane for the Startup key.
Then for "Value name" enter the letters: DLC
And for the "Value data" enter: <Progress installation path eg: C:\Progress\dlc >
To save, click OK.
Last Modified Date9/11/2018 2:32 PM

Did this article resolve your question/issue?


Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025