I have two clients with similar printing problems:

1. ERROR "519 No Print Window is Open. Close print Job.

2. ERROR "51 - No Print Window Open" and
ERROR "514 - Print Job Busy"

Both clients are trying to print and clear their posting journals so that they can close their year. Would this have anything to do with the temp folder?

Thanks,
Lars

Hello Lars,

I do not have any previous reports of these errors.

Are you printing to printer or to file? Which applications, versions and posting journals?

If they are using current versions of Adagio, a temporary file is created in the User's temporary directory. If the print has failed a number of times, there may be files lingering in this location.

The version is Ledger 8.0C and the client is attempting to print (to printer) and clear the posting journals so they can complete their year end.

~ Lars

Hi Lars,

Try cleaning out the local temp directory - this is entirely possible to be the cause. These error messages are not known.

Perhaps run CHKSYS to ensure the correct tables have been installed - you may need to reinstall the upgrade.

If you wish, make a backup of the data, then manually delete the posting journal file (GLPJRNL). After running year end, the next batch and posting sequence are reset to 1.

For unexplained reasons that are not Adagio's fault (according to Softrak), occasionally printing to File fails, returning a message just like the one you report. After that happens, even printing to Printer also fails, until you exit all Adagio modules at your workstation and re-launch.

Have the client exit and re-launch and try printing to Printer on the first attempt.

Lars:

At a client here, I found that the Crystal engine failed to clean up its temp files after trying to print to Word format. They must be deleted from the temp folder.

The printing to Word seems to fail with larger jobs.

Try downloading Cute PDF or similar program that creates a PDF "printer" and print to that.

Hi:

We had a client who had problems with the temp reporting folders. They weren't being deleted immediately - usually took 3 to 5 minutes. The visible symptom was that they could not run the same report twice in rapid succession.

The solution was to adjust the operating system. Windows XP offers the users the option to "index" their C: drive in order to improve the performance of file searches. As soon as that feature was turned Off, the problem disappeared.

Admittedly this doesn't sound exactly like your issue but it is worth checking.