Btrieve Error: Requested key not found (error=4) tripdata_setup: tripinfo_get (Thread 0)

Error: Requested key not found (error=4) tripdata_setup: tripinfo_get (Thread 0) 

This error message may be received when a trip has been deleted, however, still appears on the FOS Schedule Board. Users may receive the above Btrieve error message after selecting "Yes" to the below message. 

Solution: 

1. On the FOS Operations board, select Window-->Scheduling Defaults. 

2. In the Performance Options section, select "Debug Message (CTA Use)." 

3. Close the Operations board and open the Trips Module. 

4. Search the trip number of the deleted trip using the Trip Number search function at the top left. It will appear in the list as DELETED TRIP. 

5. Right-click on the trip and select "Delete Trip." 

6. To ensure it has been removed, close the Trips module. Open the FOS Operations board and refresh the window. 

• Related Articles

• Error: Requested key not found (error=4) sch_data_read_ac_single: aircraft_get (Thread 1)

  Error: Requested key not found (error=4) sch_data_read_ac_single: aircraft_get (Thread 1) Solution: An Aircraft Record was deleted from FOS or changed incorrectly. The record will need to be added back to FOS with the same tail and AC ID.

• Btrieve Error: Requested key not found ( error=4 ) sched_refresh_ac_lbox: aircraft_get EXA2 (Thread 0)

  Error: This error may be seen when selecting reports in Auto Report setup. Cause of issue: Aircraft ID was changed. Requested key not found ( error=4 ) sched_refresh_ac_lbox: aircraft_get EXA2 (Thread 0) Solution: 1. Restart FOS program in IMU 2. ...

• Btrieve Error: Requested key not found (error=4) schedrpt_refresch_ac_lbox: actype_get XX (Thread 0)

  Error: Requested key not found (error=4) schedrpt_refresch_ac_lbox: actype_get XX (Thread 0) Solution: The corresponding aircraft type referenced in the error was deleted. Go to aircraft type module and add the corresponding aircraft type back into ...

• 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: Invalid key number (error=6) CrewTrainingItem::SynchronizeCrewTrain… crewitem_get (Thread 0)

  Error: Invalid key number (error=6) CrewTrainingItem::SynchronizeCrewTrainingItems: crewitem_get (Thread 0) Solution: This error points to a convert button being missed during the last FOS update. To resolve this issue, all users will need to log out ...