Troubleshooting The Load Report Failed Error

Troubleshooting the Load Report
Failed Error
Applies to:
Crystal Reports 9.1 to Crystal Reports 2008 (12.0.x) when used in applicable versions of Visual Studio .NET.
Summary
There are a number of reasons for the Crystal Reports engine throwing the error Load Report Failed. This
article discusses the most likely causes for the error and possible solutions. More unusual cases are also
discussed.
Author:
Ludek Uher
Company: SAP
Created on: 16 July 2010
Author Bio
Ludek Uher is a Senior Engineer with Technical Customer Assurance, SAP
BusinessObjects. He specializes in the SDKs supplied with Crystal Reports and
BusinessObjects Enterprise.
SAP COMMUNITY NETWORK

2009 SAP AG
SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

1
Troubleshooting the Load Report Failed Error
Table of Contents
Introduction ................................................................................................................................................... 3
About the error .............................................................................................................................................. 3
Troubleshooting the four basic issues............................................................................................................ 4
Permissions............................................................................................................................................... 4
Path .......................................................................................................................................................... 4
Code ......................................................................................................................................................... 5
Heavy loads .............................................................................................................................................. 5
Troubleshooting other causes for the error ................................................................................................. 6
Retired or deprecated data connections ...................................................................................................................... 6
Invalid Formula fields ................................................................................................................................................... 6
Missing or incorrectly installed custom User Function Libraries ................................................................................... 6
Incorrectly deployed Crystal Reports runtime .............................................................................................................. 6
Missing C: drive ......................................................................................................................................................... 6
Related Content ............................................................................................................................................ 7

Useful utilities ............................................................................................................................................ 7
Useful links ................................................................................................................................................ 7
Sample applications pages ........................................................................................................................ 7
Copyright ...................................................................................................................................................... 8

2009 SAP AG

2
Introduction
There are a number of reasons for the Crystal Reports engine throwing the error Load Report Failed. This
article discusses the most likely causes for the error and possible solutions. More unusual cases are also
discussed.
About the error

Almost invariably, the error is due to one of four basic issues.
The process trying to load the report does not have permissions, either on the folder the report is in,
temp folder or registry keys.
The path given for the report in the code is invalid.
There is a coding issue.
Heavy processing load usually occuring with Web applications.
The error may be preceded or followed by errors such as:
"Unable to connect - Invalid log on parameters"

Buffer too small or missing null byte"
Other errors may also be seen before or after the Load Report Failed error.
Typically, the full error message will look like the following:
Error Details: Type : CrystalDecisions.Shared.CrystalReportsException, CrystalDecisions.Shared,
Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304 Message : Load report
failed. Source : CrystalDecisions.CrystalReports.Engine Help link : Data :
System.Collections.ListDictionaryInternal TargetSite : Void EnsureDocumentIsOpened() Stack Trace
: at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()
at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename,
OpenReportMethod openMethod, Int16 parentJob) at
CrystalDecisions.CrystalReports.Engine.ReportClass.Load(String reportName, OpenReportMethod
openMethod, Int16 parentJob) at
CrystalDecisions.CrystalReports.Engine.ReportDocument.EnsureLoadReport() at
CrystalDecisions.CrystalReports.Engine.ReportDocument.SetDataSourceInternal(Object val, Type
type) at CrystalDecisions.CrystalReports.Engine.ReportDocument.SetDataSource(DataSet dataSet)
Inner Exception -------------------------------------------------------------------------------- Type :
System.Runtime.InteropServices.COMException, mscorlib, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089 Message : The maximum report processing jobs limit
configured by your system administrator has been reached. Source : Analysis Server Help link :
ErrorCode : -2147483648 Data : System.Collections.ListDictionaryInternal TargetSite : Void
Open(System.Object ByRef, Int32) Stack Trace : at
CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocumentClass.Open(Object&
DocumentPath, Int32 Options) at
CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.Open(Object& DocumentPath,
Int32 Options) at
CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()

2009 SAP AG

3
Troubleshooting the four basic issues

Before even beginning to troubleshoot the issue it is highly recommended that the system, be it development
or runtime, is using the latest fixes and runtime. Updates as well as updated runtimes can be searched for on
the Business Objects Support Software Downloads page.
Permissions
Typically, though not exclusively, permission issues will be encountered by web applications. The process
loading the report will obviously need rights to at least read the report from its location. However, both a
winform and a webform applications require read / write permissions of the C:\Windows\temp folder (or the
temp folder defined in the system variables) as the Crystal Reports engine uses this folder to write and read
temporary files when processing a report.
The error may also be caused if the size limit on the temp folder is reached. In this case the report temp copy
will not be created and the report will fail to load.
Also ensure that the application process is able to access the parent folder containing the report. An issue
may arise if a folder has different permissions from those of the parent folder. Since the report file does not
allow for inheritable permissions to propagate from the parent folder to the report, the application cannot
access the report.
To resolve this issue
1. Right-click the report in Windows Explorer.
2. Go to the Properties dialog box > Security tab.
3. Allow the report to inherit permissions from the parent folder.
To troubleshoot possible permissions issues, use the Process Monitor or similar utility.
Path
Ensure the path to the report is correct. Take the error at the most logical face value. Often, it is useful to
hard code the path rather than use variables to see if the report is indeed available from the intended path.
When using Windows Server 2000, remember that the ASPNET account is a local account that does not
have access to network resources. In addition, the mapped drives are not available to the ASPNET
processes. Use a UNC (Universal Naming Convention) path rather than a mapped drive (for example,
\\servername\directory\).
Also, change the account that the ASPNET process uses to run applications by opening Machine.Config
and changing the user name to a user account that has permission to access network resources (for
example, 'userName="DOMAIN\username" password="users password" ').
Verify that IIS is reset.

2009 SAP AG

4
Code
Assuming the report is in the intended folder, the next possibility is that the application is not clearing the
report objects. Ensure that .close and .dispose are used on the report object(s) once the report engine is
done processing a report. Not doing so will cause memory issues that may eventually cause the Load
Report Failed error -- or worse, crash the server.
The code should look similar to the following:
private void Page_Unload(object sender, EventArgs e)
{
if (boReportDocument != null)
{ boReportDocument.Close();
boReportDocument.Dispose();
GC.Collect();
}
}
If the report is consuming an ADO .NET Dataset, ensure the dataset is also cleared periodically. For more
information on how Crystal Reports uses ADO .NET Datasets, see the article Crystal Reports Guide To
ADO.NET.
Incorrectly setting parameters at runtime may also cause the error. For example setting
ParameterFieldInfo(0).CurrentValues.AddValues() to an incorrect value will result in errors at best or
incorrect data at worst.
To troubleshoot possible parameter issues at runtime comment out the parameter code. The report will
prompt for the parameters. If the report works once the parameters are completed at the prompt, the code
will have to be adjusted.
Heavy loads
The Crystal Reports reporting engine is optimized for greatest report throughput. There are specific registry
keys that control this optimization. By default, the print job limit is set to 75 print jobs. When a heavy load is
submitted to the print engine, the 75-print-job limit may be reached and cause the error. This is most likely to
occur in Web applications. For more details regarding print jobs, see the article Crystal Reports Maximum
Report Processing Jobs Limit.
Print jobs are not to be confused with Concurrent Processor License whereby the print engine is limited to
three concurrent processes. Under high loads, this value can easily be exceeded, at which point any
subsequent requests are queued up and will wait for an available license. The more requests it has, the
longer the queue becomes, eventually leading to server slowdowns and report load failures.
If the application requires handling of high loads, consider moving to a more scalable product such as the
Crystal Reports Application Server or BusinessObjects Enterprise. For more information see the articles
Crystal Reports 2008 Component Engine Scalability

Choosing the Right Business Objects SDK for Your Needs
Scaling Crystal Reports for Visual Studio .NET
Improving Crystal Reports Performance in Visual Studio .NET Applications.

2009 SAP AG

5
Troubleshooting other causes for the error

Retired or deprecated data connections
The error may be caused by reports that use retired or deprecated data connections such as Crystal QRY
files, Crystal Dictionaries and other. Does not use report files that originally used these types of connections.
Reports based on QRY files and Dictionaries were never meant to be used in applications in any case.
Invalid Formula fields
Populated formula fields cannot be more than 32,694 characters in length. While the memo field limitation on
formula fields has been eliminated, formulas are still limited in size. Either keep the formula under 32,694
characters, or use a text field.
A blank formula field is being summarized on the report. Do not summarize on a blank formula. Test
formulas thoroughly in the Crystal Reports designer to determine any possible limits. Limits reached in the
Crystal Reports designer will not typically go away at runtime.
Missing or incorrectly installed custom User Function Libraries
See the blog Creating Crystal reports User Function Libraries (UFL) with Visual Studio .NET for information
regarding UFL deployment and configuration.
Incorrectly deployed Crystal Reports runtime
The Crystal Reports runtime can only be deployed using the runtime msm or msi files. No other deployment
is supported. For details regarding correct deployment files see the wiki Crystal Reports v. 9.1 to 12.x VS
.NET Runtime Distribution & Supported Operating Systems.
Missing C:\ drive
The application is deployed to a computer that does not have a C: drive. When the Crystal Reports runtime
is installed via the msm or msi files, certain registry values are set to point to the C: drive. To resolve this
issue modify registry values in the Registry Editor.
CAUTION!
NOTE
The following resolution involves editing the registry. Using the Registry Editor incorrectly can cause
serious problems that may require you to reinstall the Microsoft Windows operating system. Use the
Registry Editor at your own risk.
It is strongly recommended that you make a backup copy of the registry files before you edit the registry.
For information on how to edit the registry key, view the 'Changing Keys And Values' online Help topic in
the Registry Editor (Regedit.exe).
At minimum, it will be necessary to modify the following string values:
CommonFiles
Path
ConnectionDirectoryPath
ChartSupportpath
ReportDirectoryPath
The location of these string values varies depending on the version of Crystal Reports used. Search the
registry on the development computer and study the appropriate keys. Modify as needed on the runtime
computer.
To troubleshoot these issues, a utility such as Process Monitor will prove useful.

2009 SAP AG

6
Related Content
Knowledge Base articles
1218766 - Error: "Load Report Failed" when running Crystal Reports .NET application
1196436 - "Load Report Failed" when trying to deploy Visual Studio .NET 2005
1217643 - Err Msg: "Load Report Failed: Buffer too small or missing null byte"
1218759 - Error: "Load Report Failed" when trying to run Crystal Reports .NET application
1218498 - Error: "Load Report Failed" in a Visual Studio .NET web application
1197577 - Error: "Load Report failed" running a Crystal Reports XI .NET Windows application
1215038 - Err Msg: "Load Report Failed" when loading a report in an ASP.NET application
1215646 - Err Msg: "Unable to connect - Invalid log on parameters" or "Load report failed"
1205044 - Error: "Load Report Failed" when viewing reports in a .NET application
1262298 - Error "Load Report Failed" when loading report off of mapped drive and using RunAs
1426232 - File not found error experienced after deploying application
Useful utilities
Process Monitor
Charles
Fiddler
Useful links
Knowledge Base article search
BusinessObjects Articles
BusinessObjects Software downloads
SAP Crystal Solutions Support
Crystal Reports 2008 Reference
Sample applications pages
SAP BusinessObjects Code and Samples
Crystal Reports .NET SDK Applications
Crystal Reports for .NET SDK Samples wiki
NET RAS SDK Samples wiki

2009 SAP AG

7
Copyright
Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsi us, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("S AP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

2009 SAP AG

8

Troubleshooting The Load Report Failed Error

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Troubleshooting The Load Report Failed Error

Transféré par

Droits d'auteur :

Formats disponibles

Troubleshooting the Load Report

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com