Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Voyager Reporter produces "Failure Recovery Run" error and "The previous execution of the Voyager Reporter FAILED!" error when running circulation notices

    • Product: Voyager
    • Product Version: 8
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare



    When running Reporter Circulation Notices receive this error:

    Failure Recovery Run
    NOTICE! The previous execution of the Voyager Reporter
     ONLY the records retrieved from the server
     during the failed run will be processed now.
     If you wish to retrieve and process any
     NEW records which may now be on the server,
    you MUST run this job a second time to process them.


    AND running the job a second time does not provide a satisfactory result.


    Customers who have reported this error often find the solution by connecting to the Voyager server and restoring the most recent crcnotes file on the server and rerunning Reporter.

    For example:

    1. cd /m1/voyager/xxxdb/rpt
    2. Find a file that was processed. Example: crcnotes.MAIN.20190901.0917
    3. If there is no other .inp file for that print location, copy  the file from Step 2 to a .inp file extension: cp crcnotes.MAIN.20190901.0917 crcnotes.MAIN.inp
    4. Reporter should be able to find & process the file now.

    Additional Information

    Reporter should be run every day that the library is open when circjob 12 is running every day. This way the overdues/etc. will not be overlapped and sent late.

    See also Overview of Generating Reports and Notices via Reporter.


    • Article last edited: 30-Aug-2019
    • Was this article helpful?