You are on page 1of 8

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 SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 1

............................................................................................................................................................................................................................................................................................................................................................................................... 7 Sample applications pages ..........................................................................................................boc....................................................sap... 5 Troubleshooting other causes for the error .......................................................................................................... 6 Retired or deprecated data connections ..........sap...................................bpx. 8 SAP COMMUNITY NETWORK SDN .............................................. 4 Path .......................... 5 Heavy loads ....................... 4 Code .................................................................. 6 Missing or incorrectly installed custom User Function Libraries .................................................................................................................................................................................................................sap......................................................................................................................................................................................................com | BOC .......com © 2009 SAP AG 2 ......................... 7 Copyright .......................................................................................................................................... 7 Useful utilities ............................................................... 6 Missing “C:” drive ......................... Troubleshooting the “Load Report Failed” Error Table of Contents Introduction ............................................................................................................................................................................... 4 Permissions........................................................ 7 Useful links ............................... 3 About the error ............................... 6 Incorrectly deployed Crystal Reports runtime ........................................................................................................................................................................................ 6 Related Content ................................................................................................................................................................sdn............................. 6 Invalid Formula fields .................................... 3 Troubleshooting the four basic issues..............................................................................com | BPX ...................................................................................................

CrystalReports. OpenReportMethod openMethod.ReportDocument. mscorlib.Engine Help link : Data : System. This article discusses the most likely causes for the error and possible solutions. Version=2.0.CrystalReportsException. Culture=neutral.sdn.ReportDocument. About the error Almost invariably. The error may be preceded or followed by errors such as:  "Unable to connect .Runtime.Object ByRef. Int32 Options) at CrystalDecisions.0. either on the folder the report is in.CrystalReports.sap.  Heavy processing load – usually occuring with Web applications.Engine. PublicKeyToken=692fbea5521e1304 Message : Load report failed. Culture=neutral.2000.Open(Object& DocumentPath.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.CrystalReports.Engine.ReportClientDocumentWrapper.Load(String filename.ReportAppServer.ClientDoc.Shared. the full error message will look like the following: Error Details: Type : CrystalDecisions.Engine. PublicKeyToken=b77a5c561934e089 Message : The maximum report processing jobs limit configured by your system administrator has been reached.ReportClass.ListDictionaryInternal TargetSite : Void EnsureDocumentIsOpened() Stack Trace : at CrystalDecisions.  The process trying to load the report does not have permissions.COMException.CrystalReports. the error is due to one of four basic issues.EnsureLoadReport() at CrystalDecisions.ReportDocument. Version=12.ReportAppServer.Collections.Engine.com | BOC .com | BPX .Engine. CrystalDecisions. Int32) Stack Trace : at CrystalDecisions.ReportClientDocumentClass.com © 2009 SAP AG 3 . More unusual cases are also discussed. temp folder or registry keys.ReportDocument. Troubleshooting the “Load Report Failed” Error Introduction There are a number of reasons for the Crystal Reports engine throwing the error “Load Report Failed”.ListDictionaryInternal TargetSite : Void Open(System. Source : Analysis Server Help link : ErrorCode : -2147483648 Data : System. Typically.Type : System.EnsureDocumentIsOpened() SAP COMMUNITY NETWORK SDN .CrystalReports. Int32 Options) at CrystalDecisions. Source : CrystalDecisions.  The path given for the report in the code is invalid.Open(Object& DocumentPath.0.0.ReportClientDocumentWrapper.ReportAppServer.Shared.InteropServices. OpenReportMethod openMethod.CrystalReports.ReportClientDocumentWrapper. Int16 parentJob) at CrystalDecisions.sap.0.  There is a coding issue.Load(String reportName.ReportAppServer.sap.EnsureDocumentIsOpened() at CrystalDecisions. Int16 parentJob) at CrystalDecisions.boc.Collections.SetDataSource(DataSet dataSet) Inner Exception -------------------------------------------------------------------------------.SetDataSourceInternal(Object val.bpx. Type type) at CrystalDecisions.

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

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

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

NET Windows application 1215038 .NET application 1218498 .Err Msg: "Load Report Failed: Buffer too small or missing null byte" 1218759 .boc.Invalid log on parameters" or "Load report failed" 1205044 .Error: "Load Report Failed" when trying to run Crystal Reports .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 .Err Msg: "Load Report Failed" when loading a report in an ASP.sap."Load Report Failed" when trying to deploy Visual Studio .Error: "Load Report Failed" when viewing reports in a .Error: "Load Report failed" running a Crystal Reports XI .com | BOC .Error: "Load Report Failed" when running Crystal Reports .sap.com © 2009 SAP AG 7 .Error "Load Report Failed" when loading report off of mapped drive and using RunAs 1426232 .Error: "Load Report Failed" in a Visual Studio .NET 2005 1217643 .sdn.sap.com | BPX .NET SDK Samples wiki NET RAS SDK Samples wiki SAP COMMUNITY NETWORK SDN .NET application 1262298 .NET application 1196436 .bpx.NET web application 1197577 . Troubleshooting the “Load Report Failed” Error Related Content Knowledge Base articles 1218766 .NET SDK Applications Crystal Reports for .NET application 1215646 .Err Msg: "Unable to connect .

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