Kbase 15361: Incorrect Start in or Working directory causing error: Unable to Open File RBRUN.TXT (98)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/11/2004 |
|
Status: Unverified
FACT(s) (Environment):
Progress 8.x
Progress 9.x
SYMPTOM(s):
Error starting Report Builder application
Unable to Open File RBRUN.TXT (98)
** Unable to open file: <file-name>. Errno=<number>. (98)
CAUSE:
"Start in" or Working directory for the Icon invoking _printrb.p is pointing to a directory with no write access. When the _printrb.p file is invoked, it creates the RBRUN.TXT file that contains all 19 parameters that are passed to the Report Engine. You can view this ASCII file to see exactly how the parameters are being passed to the engine.
The RBRUN.TXT file (always) is written to the current working directory. The current working directory is defined as the working directory that is specified for the windows icon that was used to start Report Builder or the Progress session that it is called from. There is no over-ride available. Each user must have a unique working directory specified in the icon they use to start Progress or Report Builder.
A common misconception is that the working directory must be the directory that contains the executables for the application. This is not true. In fact, the working directory should (not) be the directory that contains the executables.
An application writes its temporary and permanent files to the working directory. It is (not) a good idea to allow write access to the directory that contains the application's executables.
FIX:
Make sure the "Start in" or "Working" directory is pointing to a write accessible directory. The directory that contains the applications executables should be in the PROPATH. This enables Progress to find the file without looking at the working directory. The working directory is used by the Report Engine to write both RBRUN.OUT and RBRUN.TXT. They are temporary files.