I/O, (290) errors

R

runnerbeans

New Member
Hi all,

I have been reading a number of posts re these, but none have 100% hit the spot.

We have a number of clients running on win2k Terminal Server.
Each system is running progress 9.1c, with the source code in a "pl" file residing on an apps server, which is Win2k Advanced Server, this also houses the DB. The DLC is located locally to each TS. Each TS is patched to service pack 3, which contains the MS hotfix for closing file's correctly (so I believe).

I list below a selection of errors that come from one DB over the a typical day. Dont read too much into each as they are really very random as to which "file" we get, the common theme seems to be mostly error 22.

Often once the errors start the only way to allow users back into the system is to reboot the terminal server(s). As the error will come up just after entering the user name and password. This does point to someting being locked on the server, but checking for open/locked files in admin tools there are none. (DB server does not need to be rebooted). We have tried setting access rights to read only, for the client DLC, this has not helped.

Progress say this is an "OS" issue, but i wonder if it is the same sort of "OS" that the prowin32 gpf's that you used to get with graphics issues. (which were cured for us by upgrading progress, not the graphics driver). What i mean is is there a conflict between Progress and win2k TS? The problems can not be corrupt r code, or hardware related, as each system is totally separate. The problem must lie within Progress or win2k TS itself.

16:54:36 SRV 10: SYSTEM ERROR: I/O error 9 in writeto, ret -1, file 6(srt), addr 0. (290)
08:43:45 SRV 5: SYSTEM ERROR: I/O error 22 in readit, ret -1, file 21, addr 0. (290)
15:58:27 SRV 9: SYSTEM ERROR: I/O error 22 in readit, ret -1, file 20, addr 0. (290)
09:49:59 SRV 6: SYSTEM ERROR: I/O error 22 in readit, ret -1, file 7, addr 0. (290)


Ideas would be welcome...
 
Idea! :idea:

What is the application startup directory? If this is a network drive on the apps server, try using -T to set the temporary file directory to a local drive to the client. This may fix a couple of things. The performance should pick up a bit and the problems with the .srt file may go away.

Alternatively - pick a single workstation that appears to have the problem and install the application to the local drive and configure it to run from there. If this fixes your problem then it may be network related rather than O/S or Progress version

Toby
 
I/O (290) errors

Just an update on these errors, with win2k TS.

It does now seem certain this is in fact a bug within the OS. MS have identified the problem in Q272582, which they say to have been fixed in SP3. However there is another later unresolved problem, which is almost identical, but according to the MS KB is still unresolved (Q294816).

So the outcome is have no network shares, or application files on a remote server. A Pain, but until the bug is resolved this looks to be the only way around the problem.


:eek:
 
Hi,

You are right the -T did help but did not cure. We had ALL application files and the -T local to the TS, each user had their own promsgs and ini file, with the TS patched to SP3 but still got the errors. In the end we found one area, where the propath, could get apended to reference a network share. We found a way around this and bingo no more errors... (touch wood)





:D
 
In the client login it should set up a drive (W I think) which points to a unique directory per client. You should point the -T at this.
 
You are correct here, also. Each user must have, and did have their own temp dir.


Other problems you may experience on TS if users share a temp dir can be the dreaded 1124 DB corruption error. Normally hardware, but on TS can be if you try and share a temp dir.
 
You must log in or register to reply here.
Back
Top