on 04-15-2009 12:32 PM
Hi all,
I have following problem:
unexpectedly one report became very slow - but only on some computers.
The report remains quick on other computers.
Other reports - also with input parameters - run normal.
I have found where this delay happens - this is a first call of a report.setParameter method.
The delay is between 40 und 80 seconds.
Does anybody have an idea what is wrong with my report or with those computers?
Any help will be valuable.
Thanks in advance.
Hier is a technical information:
VB.NET Winfroms Application
.NET Framework 1.1
Crystal Reports 11 Release 1
the report's data source is a MS SQL Server database table
Data Access driver is ODBC based on SQL Native Client.
The CR distribution package is about 3 years old. On two machines we have very good values on others is an extremely slow execution of reports.
Example (always the same report / same database / same CR runtime / same SQL Native Client version):
ColdStart means including first atart of the CR Runtime
Warm means that the runtime is already loaded
____________________ColdStart (in sec)_____Warmstart (in sec)
Machine 1:________________ 5________________ 3
Machine 2:________________90________________55
Machine 3:________________95________________60
Machine 1 has the Windows XP Prof SP2,machine 2 & 3 have the Windows XP Prof SP3.
- VB Net 1.1. SP1
- CR XI Rel 1
- SQL Server 2005 09.00.3042
- SQL Native Client 09.00.2040
The comparison with modules.exe brought no major differences. The mysterious waiting time of 40-60 sec at Machine 2 & 3 arises here:
31.03 02:19:38.0358 // StartPrint Button
31.03 02:19:39.2389 // Start Loading Crystal Report Viewer
31.03 02:19:39.3483 // Load and set some variables
... mysterious waiting time 40-60 sec, here only 38 sec ...
31.03 02:21:17.8802 // set the frist parameter with
31.03 02:21:17.8802 // set other parameters, overwriting dsn ...
31.03 02:21:19.9271 // End Loading the Crystal Reports Viewer / Visualization results
What could be the cause? We have this problem on the most computers.
We are really desperate. We can not continue. : (
With best regards
TATIANA
Hi Tatiana,
Might be Windows xp SP3 be the reason.
As Crystal Reports XI is not yet tested with Windows XPsp3.
Crystal Reports XI is supported with following operating systems:
u2022 Windows XP SP1 Professional
u2022 Windows XP SP2 Professional
u2022 Windows Server 2003 Datacenter Edition
u2022 Windows Server 2003 Enterprise Edition
u2022 Windows Server 2003 Standard Edition
u2022 Windows Server 2003 Web Edition
u2022 Windows 2000 SP4 Professional
u2022 Windows 2000 SP4 Advanced Server
u2022 Windows 2000 SP4 Datacenter Server
u2022 Windows 2000 SP4 Server
*u2022 Windows Vista (All Editions)
Crystal Reports XI R1 SP4 needs to be applied
Regards,
Shweta
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No response for 3 months, closing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tatiana,
Also check the report options. Make sure that the Verify on first refresh or any of the Verify options are checked off in the RPT files.
Also check the registry:
HKEY_CURRENT_USER\Software\Business Objects\Suite 11.0\Crystal Reports\DatabaseOptions and the 4 Verify keys are all set to No.
You may want to turn on SQL Profiler and watch what the "bad" PC's are doing that is different compared to a "good" PC. Watch the Functions each are using and the SQL being sent from each PC to see if it's different. If it is then possibly one of those reg keys need to change or you do have differences in the database client.
SLQ Server 2005 does require the Client to be installed if using the native driver.
I also assume when you designed the reports you did select Crystal Reports ODBC driver correct?
Thank you
Don
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'd compare the runtime, both Crystal Reports and non Crystal reports. I suspect either the CR runtime will be different or the database client will be different. Use the Modules utility to do the comparison. Modules can be downloaded from here;
https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip
Ludek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Understood. However, there obviously is a difference between the machines. A really easy way to tell basic differences is to use the Modules utility. For me, that is always step number one in these types of issues. Once that is eliminated as a cause, we can move on to more complex tools such as Process Monitor and so on. But I'd start with the basics.
Ludek
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.