Progress KB - Application terminates with 290 error errno 2




Feedback
Did this article resolve your question/issue?

   

Article

Application terminates with 290 error errno 2

« Go Back

Information

 
TitleApplication terminates with 290 error errno 2
URL NameP117101
Article Number000129447
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: 10.x, 11.x, 12.x
OS: All supported platforms
Question/Problem Description
Application terminates with 290 error errno 2
SYSTEM ERROR: I/O error <n> in <program>, ret <n>, file <n>, addr <n>. (290)
SYSTEM ERROR: I/O error 2 in readit, ret <n>, file <n>, addr 0. (290)
The same application runs fine on other systems.
Filemonitor does not show any problem in finding the file

Server log might contain something similar to the following:
(Procedure: '<procedure name>' Line:1773) SYSTEM ERROR: I/O error 2 in readit, ret 78169, file 18(<file name>), addr 0. (290)

A stack such as the following might be included in a protrace file:

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]

Steps to Reproduce
Clarifying Information
Error MessageSYSTEM ERROR: I/O error <n> in <program>, ret <n>, file <n>, addr <n>. (290)
SYSTEM ERROR: I/O error 2 in readit, ret <n>, file <n>, addr 0. (290)
Defect/Enhancement Number
Cause
Corrupted r-code.
Resolution
Replace corrupted r-file

To find which piece of code is causing the problem use a 3rd party tool or Operating System tool to find the filehandle in order to further analyze which file is causing the error..

UNIX: Use lsof against the PID of the Progress Session.
Windows: Use the Handle tool from MicroSoft Sysinternals  
(https://docs.microsoft.com/en-us/sysinternals/)

Using Progress start the client with -yx startup parameter to see what procedures are being run and re-compile those procedures.
Workaround
Notes
References to other Documentation:

Progress Articles: 

000001645, How to find out the meaning of a Windows error number.

Articles merged with this article: 000021469
Last Modified Date5/7/2020 7:36 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.