Actually, the hot fix will not help in this situation - it addressed a scenario with the batch control file that contained an error.

If the posting journal cannot be printed but there is an indication that one exists, there are two possible reasons. When do you get the message - immedately when selecting the posting journal from the menu, or do you get the posting journal screen with a range of sequences, and clicking print gives the error? The timing of the message indicates which issue you have.

If you immediately get an error, this indicates that the program thinks there is no posting journal to print, but the underlying data file has more than zero bytes in it. This is often due to the system holding on to the file and not letting Adagio purge it when it was printed. The solution is to exit from Adagio and manually remove the file. Adagio Ledger 90 posting journal data files start with GLPJ. Don't delete files (just in case) but rename the data extension.

If you get to open the posting journal screen, this indicates that the program thinks there is a posting journal to print but it isn't there. This is often due to the underlying posting journal file being deleted manually rather than letting the program purge the report. The solution is a little more tricky - you have to post something else (even a zero-dolar entry) to add something else to the posting journal. Then you can select all sequences and print and purge.

In Adagio Ledger 90B, you might be able to solve this by disabling the 'allow purge of posting journals' option in the company profile. Disabling this means that posting journal files are automatically purged during the Year End process, meaning that you don't have to 'print and purge' all the posting journals to be allowed to do year end.