Skip to Content
0

Method ReportDocument.Load() consumes a lot of time when taking SQL server down

Jun 23, 2017 at 04:40 PM

51

avatar image

I am using Crystal Report XI developer version 11.5.8.826, and facing with very weird problem. Method ReportDocument.Load() becomes very slow when the application is deployed in machine that does not have SQL server installed. The application and rpt file is placed in the same machine.

Although I have tried many ways, such as check option "No Printer", uncheck option "Save Data With Report", "Verify On First Refresh", it still not fixes this problem. This issue is similar with the described in thread

https://archive.sap.com/discussions/thread/3888228. Unfortunately, it also not help in my case.

I found that when ReportDocument.Load() is called, it try to verify the SQL Server that prior linked to this report during design stage, in my case is localhost. However in production, SQL server is not deployed in the same machine with application, therefore, crystal report keep trying to lookup non-existent SQL server until the timeout reached. I think method

ReportDocument.Load() should not touch database at this time, the logon information to SQL Server will be set in next step.

And the most weird thing is some other reports in my machine do not get this problem although they were designed in totally the same way, same setting , same Crystal Report application version.

Really appreciate if any body have solution for this issue. Thank you and Best Regards.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Don Williams
Jun 23, 2017 at 09:09 PM
0

We fixed that in current versions of Crystal Reports and CR for VS.

Use the latest CR for VS 2010 -> 2015 .NET and it all stops verifying the DB on open unless you tell it to.

Don

Share
10 |10000 characters needed characters left characters exceeded