Load report failed.

[Former Member]

Hi to all,

I'm using Visual studio 2005-C#,Asp.net2.0 and Crystal

Report 11.5 and SQL Server2005.

I added tables,fieldobject dynamicaly to the crystal

report, my problem is wheever i load the crystal report using Reportdocument object then i get the error as Load report failed.

Sample Code:

ReportDocument boReportDocument;

ISCDReportClientDocument boReportClientDocument;

//Create a new ReportDocument

boReportDocument = new ReportDocument();

// load the RPT file

boReportDocument.Load(Server.MapPath("~//Success//CR_VerticalDesign.rpt"));

//Access the ReportClientDocument in the ReportDocument (EROM bridge)

boReportClientDocument = boReportDocument.ReportClientDocument;

Whenever the Load method is calling then the following error has raised

Load report failed.

at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()

at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename, OpenReportMethod openMethod, Int16 parentJob)

at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename)

at JBProduct.NQ.ExportToExcelController.AddTableToCrystalReport() in D:\projectname

I came to know we should give some permission to AspNet for the virtual directory but my client is not accept this solution.

I came to know one more solution we add the following code to web.config

<identity impersonate="true" userName="domainname/username" password="password" />

This username is Admin username of the server so my client is not accept this option also.

Experts please help me, how to solve this problem without giive any permission or add username.

[Former Member · Accepted solution]

Hi;

If it is a permissions issue, there is no other way around it. You can try running Microsoft's Process Monitor tool to determine if it is in fact a permissions issue, but it sounds like you already know that it is.

Best Regards,

Jonathan

[former_member11696 · Accepted solution]

This is Microsoft Security issue. There is no way around it, you would be considered a trojan or virus by working around MS's security, that's way the cusomer id blocking your app.

You need to discuss with the customer what a usable security level would be to enable users have access to your application.

Possibly creating a new "Crystal" user you can run your app in and create DB access that is limited to what the app requires only.

[Former Member · Accepted solution]

Hai Williams and Jonathan Parmin,

Now what i did is just add this line in the

web.config file. I dont know this is right or wrong,

<identity impersonate="false" ></identity>

By default impersonate is true, i change this into false now it's working without give any permission for ASPNET/give any

username and password in web.config.

if i use this in the production server then will any problem raise?

Thanks in advance.

[Former Member · Accepted solution]

Experts please tell me,

<identity impersonate="false" ></identity>

this code raise any problem or not in the prodcution server.

Thanks in advance