Status: Verified
SYMPTOM(s):
ERROR 290 running a 4GL application
Error 290 with I/O error 2 when running a .r
SYSTEM ERROR: I/O error 2 in <program>, ret <n>, file <n>, addr <n>. (290)
SYSTEM ERROR: I/O error 0 in readit, ret <n>, file <n>, addr <n>. (290)
SYSTEM ERROR: I/O error 13 in readit, ret <n>, file <n>, addr <n>. (290)
SYSTEM ERROR: I/O error 9 in readit, ret -1, file <n>, addr 0.(290)
stacktrace from _progres reads:
readitb
crgenLoad
crLoadSeg
For example:
PROGRESS stack trace as of Thu Feb 1 12:44:30 2007
Command line arguments are
/users/dlc10/bin/_progres -pf scripts/update.pf
( 0) 0x400000000078b37c uttraceback + 0x24 [/users/dlc10/bin/_progres]
( 1) 0x400000000077e160 uttrace + 0x1d0 [/users/dlc10/bin/_progres]
( 2) 0x400000000077df38 utcore + 0x120 [/users/dlc10/bin/_progres]
( 3) 0x40000000001a9290 drexit + 0x280 [/users/dlc10/bin/_progres]
( 4) 0x40000000001a44e0 msgout + 0x3e8 [/users/dlc10/bin/_progres]
( 5) 0x40000000001a3db8 msgn + 0xd8 [/users/dlc10/bin/_progres]
( 6) 0x400000000077516c readitb + 0xcc [/users/dlc10/bin/_progres]
( 7) 0x4000000000775090 readit + 0x18 [/users/dlc10/bin/_progres]
( 8) 0x40000000004cb0ac crgenLoad + 0xfc [/users/dlc10/bin/_progres]
( 9) 0x40000000004caa58 crtxsLoad + 0x220 [/users/dlc10/bin/_progres]
(10) 0x40000000004ca360 crLoadSeg + 0x230 [/users/dlc10/bin/_progres]
(11) 0x40000000004c6c80 crload + 0x258 [/users/dlc10/bin/_progres]
(12) 0x40000000004c4eb0 crpsrch + 0xc90 [/users/dlc10/bin/_progres]
(13) 0x40000000004c34dc crrun_entry + 0x1a4 [/users/dlc10/bin/_progres]
(14) 0x400000000051cc44 rninterpret + 0x6c [/users/dlc10/bin/_progres]
(15) 0x40000000001e490c rnrq + 0x84 [/users/dlc10/bin/_progres]
(16) 0x40000000001a25d4 main + 0x2ac [/users/dlc10/bin/_progres]
(17) 0xc0000000000218b0 $START$ + 0xa0 [/usr/lib/pa20_64/dld.sl]
Errno = 13 reads as follows from the Microsoft "C" compiler's errno.h file:
13L ERROR_INVALID_DATA The data is invalid.
CAUSE:
The r-code is corrupted
FIX:
Replace the .R code.
To find out what piece of code is causing the problem use a 3rd party tool or operating system tool.
On UNIX, use the lsof command against the PID of the Progress Session.
On Windows, the Handle tool from Sysinternals (http://www.microsoft.com/technet/sysinternals/default.mspx) can be used to analyze which file is causing the error.
Using Progress start the client with -yx startup parameter to see what procedures are being run and re-compile those procedures.