Contents x
    Error: System Error: I/O errors - logging into or using FIMS
    • 05 May 2023
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Contents

    Error: System Error: I/O errors - logging into or using FIMS

    • Updated on 05 May 2023
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Article summary

    FIMS users may receive various System I/O errors when using FIMS:

    The following error may also occur while using FIMS:

    You may also see this error:
    SYSTEM ERROR: I/O error 2 in writeto, ret, -1, file (...tempfiles\...), addr

    You may see these errors occur on the front end of FIMS in the form of windows that pop up, you may also see these in Event Viewer, database logs, or Protrace logs.
     

    Answer:
    This message can indicate several issues and root causes:

    1. The server or terminal server the user is connecting through, has undergone a backup or snapshot while users were logged into FIMS.  The server will need to be rebooted before users are able to use FIMS.

    See this progress solution articlefor more details.
    • If you are doing a full server backup, it is suggested to create a scheduled task on the FIMS server, which stops the databases in the evening, and turns them back on after the backup/snapshot is complete.
    2. This error can also occur on a terminal server and the issue with writing temp files across the network on the database server. A solution is to write the temp files locally. To fix that, try the following:
    • Create a tempfile folder on the terminal\RDS server, for example, C:\tempfiles
    • Go to the database server, npo\found\ConfigFiles, make a copy of the wfound.pf file and name the copy something like wfound-ts.pf.  
    • In the new wfound-ts.pf file put in the path to the terminal server local drive where you want temp files to be stored there, you may need to use a UNC path there to the TS. Here is what it looks like by default.
    Note that a relative path is used for temp files which points to the database server across the network:

    Here is how the temp files location would look in the wfound file if using a local path: 

    3. Update the FIMS shortcut on terminal server to point to that new edited wfound-ts.pf file. After applying that change, be sure to right-click and run FIMS as admin on the TS and wait for the database selection screen to appear, then you can cancel. That needs to be done to update the registry on the terminal server.

     Here is how you configure the FIMS shortcut. Note for this issue, you will not use the out of box wfound.pf, you will use the new one you created:
    How do I create a FIMS shortcut on a workstation, terminal server or the database server?
     

    4. Then you can run FIMS normally and the errors on the terminal server should go away.


    Please see the following Progress discussion on this issue:
    https://community-archive.progress.com/forums/00026/36494.html 


    Was this article helpful?
    What's Next