Launchpad - Troubleshooting - Won't Export Crystal Reports

Launchpad - Troubleshooting - Won't Export Crystal Reports

Scheduler stops Exporting

If Launchpad suddenly stops exporting reports (even though reports are still running fine), the issue may be that the TEMP directory on the server is full. Newer versions of Launchpad should automatically clean up the directory, though this can sometimes stop working.

The default TEMP directory is defined by the %TEMP% variable for a user, it defaults to C:\Users\[username]\AppData\Local\Temp. For a system account on the server like IIS, it would be: C:\Windows\Temp.

There is a limit on the number of TEMP files because the way the names are auto-generated. The file names are in the format of "tmp0000.tmp" through "tmpFFFF.tmp"—the 4-digit hex number imposes a limit of 64k files. 

Check the C:\Windows\Temp directory on the server running Launchpad for 64k temp files - older files can be deleted to get things running again.

Check that the latest version of LaunchPad is installed, as the print services must be run in x64 mode.  (v1100.1001 and up)

    • Related Articles

    • Launchpad - Release Notes

      version: 1100.1002 Date of Release 2026.03.04 Utilizes Crystal Reports x64 now at service pack 39 Fix issue with LaunchPadSchedule not showing all data entry points on some user displays. The UI will now show scroll bars to allow user to scroll ...

    • Launchpad - Login Prompt when running report

      Problem: When running a Report in Launchpad you recieve a Login prompt. Solution: Set the Database connection to use the OLED DB (ADO) for the DB Connection There you will choose the Corresponding OLE DB Provider for the Database Engine SQl Server = ...

    • Launchpad Scheduler - User Guide

      Launchpad Scheduler Guide In this guide the steps for creating a Basic Scheduled Report job as well as advanced Configuration Creating a New Scheduled Job Click on the New Job icon Task Give the Task Description a Name Click Save Schedule Click on ...

    • Maximum report processing jobs limit reached error

      If this error is ever encountered: It is due to the Print Job limit being hit. By default, it is 75. Once this value is reached, the above error will happen and IIS will need to be reset in order to get Launchpad working again. The Job limit can be ...

    • Launchpad Updater 530 Not logged in Error

      Older versions of Launchpad may receive this error when trying to update: Download this and deploy to the Launchpad root directory (overwriting what's there) to correct this. WebAppUpdateUtility.exe and WebAppUpdateUtility71x.exe are obsolete and ...