Need help with "Query Engine Error"

[AZdesertdog]

Using CR10/CE10 with MSSQL2k db

I have scheduled instances of a report and several of the instances that have large data parameters are failing with the following error:

"Query Engine Error. File D:\Program Files\Crystal Decisions\Enterprise10\Data\procSched
\corpreport.reportjobserver\~tmp116c39e32113020.rpt"

The report has several subreports and usually takes 1-3 hours to run depending on the params but I've never had it fail in the past. Any help appreciated.

 

[synapsevampire]

What does large data parameters mean?

A string parameter with a large amount of text, multiple value parameters with lots of entries, or?

-k

 

[AZdesertdog]

Probably didn't explain that very well. I run the report multiple times with different divisions as the parameters. Some divisions are very large (many data rows) and others are small. The reports for the larger divisions are bombing.

 

[patmondor]

Anytime you have a query engine error....it is due to the passing of a parameter via an odbc driver and the driver is telling you...no can do. I have seen this only with reports that have sub-reports and in my case integration with a Remedy database. In my case the Crystal odbc driver simply wasn't compatible with the Remedy odbc driver we were using in our subreports.

Break the report up.....can you run the main report without errors? How about the subreports....? Save the subreport as a standalone report and run it...does it produce the error....? Again, everytime I have seen this it was due to an odbc driver compatability issue.

 

[synapsevampire]

Pat: "Anytime you have a query engine error" This is not true.

jpoulos: The first thing I'd do is apply the service packs:

http://support.businessobjects.com/fix/hot/si75/default.asp

Your next step would be to see what the server is returning for the report, and to make sure that the record selection formula is being passed to the database (check Database->Shwo SQL Query, it should reflect the criteria in the record selection formula).

Also qualify your statements, "many rows" is relative, stat specifics, does that mean more than 10, 100, 1000, 10000, 100000, 1000000...

Does it fail in CR and in CE, or just CE?

Are you checking the Event Log for more details?

Have you done a trace on the database to determine if it's failing on that side?

-k

 

[patmondor]

synapsevampire - don't want to get in a post war here...but please qualify "not true". If you go to

http://www.businessobjects.com

....go to the knowledge base and type in Query engine error. Every article talks about either a problem with the odbc driver on the Crystal side of things....or a third party ODBC driver..such as Remedy, Oracle, SyBase.

Service Packs and Hotfixes could cure this issue....due to the fact that they replaces the CR_odbc.dll that makes these type of connections. However, a third party driver might be the offender. He didn't state what driver the subreports use (could be 3rd party). For example running CE10 SP1 with Remedy 4.x will not work. Remedy will even tell you that this is the case. Remedy 5.x patch 1308 and above is certified to work with Crystal Enterprise 10. I couald install every service pack under the sun...bottom line an old remedy odbc driver would never allow me to make the connection. It is possible in this case that the appropriate third party driver would need to be updated to work with Crystal.

Good call on trying to run the report in CR and CE, but since both will be using the same odbc connections....the error will persist.

 

[patmondor]

synapsevampire - don't want to get in a post war here...but please qualify "not true". If you go to

http://www.businessobjects.com

....go to the knowledge base and type in Query engine error. Every article talks about either a problem with the odbc driver on the Crystal side of things....or a third party ODBC driver..such as Remedy, Oracle, SyBase.

Service Packs and Hotfixes could cure this issue....due to the fact that they replaces the CR_odbc.dll that makes these type of connections. However, a third party driver might be the offender. He didn't state what driver the subreports use (could be 3rd party). For example running CE10 SP1 with Remedy 4.x will not work. Remedy will even tell you that this is the case. Remedy 5.x patch 1308 and above is certified to work with Crystal Enterprise 10. I could install every service pack under the sun...bottom line an old remedy odbc driver would never allow me to make the connection. It is possible in this case that the appropriate third party driver would need to be updated to work with Crystal.

Good call on trying to run the report in CR and CE, but since both will be using the same odbc connections....the error will persist.

 

[synapsevampire]

It's certainly returned as a result of querying the database, but the cause isn't "it is due to the passing of a parameter via an odbc driver and the driver is telling you...no can do"

Adding to this, the error is generic, for instance your search should have returned this error using native connectivity:

http://support.businessobjects.com/library/kbase/articles/c2013709.asp

I'm not in a post war, nor pre war just trying to clarify. Later in your post you stated that it's your experience, which makes sense, but to state it to always be the case is incorrect.

Also note that the post states that the reports fail when they are large, which might make sense for various reasons, including timeouts.

-k