eRAMP I/O Error 123

I/O Error 123

Problem: When starting eRAMP you get an I/O Error 123.
Cause: eRAMP is trying to open a file that is missing from the expected folder location.

Resolution: Delete file eRAMPDAT.INI file in C:\Users\Public\ERAMP_DATA and then start eRAMP.exe. A new eRAMPDAT.INI file will be created by restarting eRAMP after deleting the file. The new file will have the proper information to eliminate the error.

    • Related Articles

    • I/O Error 123

      Applies to: eRAMPSQL and eRAMP Standard Problem: When starting eRAMP you get an I/O Error 123. Cause: eRAMP is trying to open a file from an incorrect folder location. In other words eRAMP is looking in the wrong place for a specific file to open ...

    • I/O Error or I/O Error 32 when importing a file

      Applies to: eRAMPSQL and eRAMP Standard Problem: When importing loans into eRAMP an I/O error displays.   Cause: The file being imported was open in another program like Excel, Word or Wordpad. When trying to import a file that is open in another ...

    • I/O Error or I/O Error 32 when importing a file

      Problem: When importing loans into eRAMP an I/O error displays. Cause: The file being imported was open in another program like Excel, Word or WordPad. When trying to import a file that is open in another program into eRAMP Windows will generate an ...

    • DBNETLIB error

      PROBLEM: After moving eRAMP SQL version to a new workstation upon startup there's an error message DBNETLIB connection failed. eRAMP does not connect to the SQL DB. No loan data is visible in eRamp. CAUSE: The ERAMPDAT.INI file is missing from the ...

    • SSPI Error generated by SQL Server

      The SSPI Error is generated by SQL Server. SSPI is Security Support Provider Interface.   The eRAMP connection string is:       'Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=false; Initial Catalog=ERAMP;Application ...