Btrieve Error - I/O error during disk read/write (error=2) vcl_display_comment: comment_get (Thread 0)
Error: Btrieve Error - I/O error during disk read/write (error=2) vcl_display_comment: comment_get (Thread 0)
Resolution: In the FOS Data Folder rename these two btr files: comment.btr and comment2.btr to ".old." Then under the login window -> select utilities -> Create Files -> Comment and Comment2
Related Articles
Btrieve Error: I/O error during disk read/write (error=2) audtrail: btrieve_status(Thread10428) (Thread 0)
Error: Btrieve Error: I/O error during disk read/write (error=2) audtrail: btrieve_status(Thread10428) (Thread 0) Solution: Error message is received upon login to FOS for all users. Clear all Pervasive Sessions and/or reboot the FOS server.Btrieve Error: I/O error during disk read/write (error=2) audtrail: btrieve_status(Thread10428) (Thread 0)
Error: Btrieve Error: I/O error during disk read/write (error=2) audtrail: btrieve_status(Thread10428) (Thread 0) Solution: Error message is received upon login to FOS for all users. Clear all Pervasive Sessions and/or reboot the FOS server.Common Btrieve Errors
1 – Normally the temp directory is set to another location besides the data server. The path may be changed in the ‘Utilities’ menu at the login window. 2 – The file is corrupted. The error message should indicate which file. The file must be sent to ...Btrieve Error: Requested key not found (error=4) sch_data_read_ac_single: aircraft_get (Thread 1)
Error: This error may be seen when opening Operations Requested key not found (error=4) sch_data_read_ac_single: aircraft_get (Thread 1) Solution: When this error occurs when opening the Operations Page/Schedule Board the user will need to log out of ...Btrieve Error: Couldn't change dir during expansion (error=35) FOS can not open the Btrieve data files.
Error: Couldn't change dir during expansion (error=35) FOS can not open the Btrieve data files. Use the Utilities | File Locations pull down menu to set the Data and Temporary Directories. password_init: compinfo_open (Thread 0) Solution: Ensure that ...