Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CE 9.0 Report Fails "Failed to open a rowset"

Status
Not open for further replies.

wilsonmichael

Programmer
May 29, 2002
21
US
When running this one report i sometimes get this failed message "Failed to open a rowset. File D:\Program Files\Crystal Decisions\Shared\Temp\procSched\USMEADMGFISPCD1.report\~tmp11c834f5d929860.rpt."

This message occurrs after the report has been running for 30 minutes. Is there some kind of timeout for long running queries?

I have checked the database and i do see a long running query but there is output that is being written. The error found in oracle is a lost connection error.

System Details
I am running crystal enterprise 9.0 with oracle 9 database.
using odbc driver CR Oracle Wire Protocol ODBC Driver 4.10

The report i am running contains a stored procedure. I pass three parameters to the procedure. These 3 parameters are a Userid, a report_id and a seq_id. These parameters are telling the proceudure where to get the data to run from.

Thanks
Mike
 
Hi,
It looks like you connection to Oracle is Timing Out..There is a setting that drops 'idle' connections after some period of time and since no data had been returned yet, the connection is seen as idle..
In the CMC go to Manage Servers and check the timeout setting on the Pageserver...
But before changing it, you may want to be sure your SP is as efficient as possible so that the query does not take so long..how many records, on average, are involved?

[profile]
 
The setting for the page server says 20 minutes.
so after 10 minutes of activity it seems to go idle
until it fails after 30 minutes

I ran this report with the same criteria and data in our benchmarking environment and it ran in 7 minutes. Returned 2600 rows. The data in both environments are the same.



 
Could it be a difference in indexes between the two DB environments. Also the timeout issue was a bug in CR crdb_ADO.dll until 9.1.1.450. I don't recall if there was a similar issue with other DB Drivers.
 
currently there are no indexes on the tables the procedure uses in either environments
 
What was the timeout bug yu speak of and what hotfix was this fixed in
 
The bug was that the error "Failed to open a rowset" occcurrs when a report is based on a stored procedure that requires greater than 30 seconds to process. It was fixed in the hot fix cr10netwin_en.zip on 12/5/2002.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top