Crystal Reports – Load Report Failed Error
Our team here at remiWare has worked with Crystal Reports for over 10 years. In that time, we know that if you use an application that utilizes the SAP/Business Objects Crystal Reports Runtime Library for Microsoft .NET then chances are that you have come across the dreaded “Load Report Failed” error before. This is very common when the application is used to schedule Crystal Reports.
The problem with this error is that it can happen at the most random times and the error stack trace offers little to no useful information at all. It can happen when trying to open and load a Crystal Report for viewing or when loading it for execution.Over the years, we have come across this error several times and have found resolutions to it about 99% of the time.
Here are the top fixes for this dreaded “Load Report Failed” error:
1. Too Many Files in the Windows TEMP folder
- When a Crystal Report is loaded into memory by an application via the runtime library, one of the options is to do so using a temporary copy. This is good practice because you really don’t want your code to fail because the user had the report open elsewhere. When this happens, the Crystal Reports Runtime Library create a copy of the report and places it in the Windows TEMP folder. Unfortunately thats where the good news ends as the runtimes DO NOT clean up after themselves. If your application runs a lot of Crystal Reports, like remiCrystal does, the TEMP folder will quickly fill up with these temp files. Once the number of these temporary files reaches a certain level, the Crystal Reports runtime library will throw the “Load Report Failed” error. The solution to this is to basically clear out the said folder.
2. PrintJobLimit Value Exceeded
- So you have checked the TEMP folder and it all looks good. Whats next? The Crystal Reports Runtime Library has a configured limit of how many jobs it can process in a given session. The default value is 75 and once any application goes over this, you guessed it, Load Report Failed! Fortunately, this limit can be overridden in the registry by navigating to HKEY_LOCAL_MACHINE/SOFTWARE/Business Objects/Suite 12.0/Report Application Server/InprocServer. Find the PrintJobLimit Key and set it to –1 for no limit (if you are using Crystal Reports 2014, change Suite 12.0 to Suite 14.0 accordingly).
3. Bad Code
- If the developer that is utilizing the Crystal Reports Runtime Library is careless and does not properly dispose off the Crystal Reports objects in memory then the “Load Report Failed” error will occur. In that case, log a bug call with them and tell ’em we sent you!
4. Bad Report Objects
- Sometimes things in the Crystal Report RPT file are just not as they should especially when its complex and there are multitudes of sub-reports involved. There is really no straight solution to this one other than removing objects from the Crystal Report one at a time until the “Load Report Failed” goes away. Once you find the offending object, you should be able to figure out what the issue is. We have in the past found causes to range from bad main report to sub-report parameter links to invalid hyperlinks.
If you would like to give remiCrystal a try, you can download the 14 day free trial from here.