Your request could not be completed because a failure occurred while t 1

[rereis]

Getting the following message when running this particular report from Iview BO enterprise XI

Your request could not be completed because a failure occurred while the report was being processed

Reports runs fine if I run from crystal reports from my machine.

My guess is I am running out of some resources but not sure which any suggestions will be appreciated.

Thanks

 

[MJRBIM]

Are you SCHEDULING an INSTANCE to HISTORY, or are you trying to VIEW-ON-DEMAND...?

Try both methods and see if they give you the same errors.

 

[rereis]

I was trying VIEW-ON-DEMAND and did not work

now if I SCHEDULE it works. Of course when I schedule I have to set the parameter when I VIEW-ON-DEMAND I have to pick the parameter from a list.

What does this tell us?

 

[MJRBIM]

That's what I expected. What it tells us is that it is not a problem with the RPT file - or the connection to the database (as both of them are OK when you schedule).

A few more questions to help nail it down -

1.) How long is your scheduled report taking to run, and how may records does that instance return...?

2.) Do you error-out when doing View-On-Demand before or after the parameter prompt?

3.)Is the View-On-Demand error instant, or does it it run for a while - then give the error?

 

[rereis]

1.) How long is your scheduled report taking to run, and how may records does that instance return...?

Taking about 10 minutes to run it returns 19 records but it goes through over a 100 thousand records. (Not sure if it is important but there are 3 subreports in this report)

2.) Do you error-out when doing View-On-Demand before or after the parameter prompt?
After the parameter is prompt, the list is a static list that was imported when creating the parameter field

3.)Is the View-On-Demand error instant, or does it it run for a while - then give the error?

runs for about 15 to 20 minutes

 

[MJRBIM]

A report that runs for 10 minutes should never be permitted to View-On-Demand. On-Demand reports should have a max run-time of under 2 minutes.

You should have your users schedule it with parameters and then view the restulting Instances from History.

 

[rereis]

And there is no way around the 10 min limitation? what sets this limit?

 

[MJRBIM]

The limit is really a business-rule, a report isn't ready for "On-Demand" refresh if it takes 10 to 20 minutes to run. Our business-rule is under 2 minutes, or they have to use the SCHEDULE "NOW" function and enter the Parameter values.

The physical limits are set on the Page Server and the Cache Server settings in the CMC. Also, can be on the Report Application Server (RAS) depending on how you are accessing the RPTs and which viewer you are using.

Look for the following settings -

Minutes Before an Idle Connection is Closed:
Minutes Before an Idle Report Job is Closed:
Database Records To Read When Previewing Or Refreshing a Report:
Records limited to:

You may also want to talk to your DBAs about creating a VIEW or a STORED PROCEDURE that can extract your 19 records from the 100,000+ record set more efficently than the RPT file going against the underlying tables.