I'm working on a report that uses a long running sql server stored procedure. When I run the focus procedure the web page request seems to be timing out. I know the report works because if I hard code a record in the stored procedure the report runs fine. Is there a way to control the request timeout for reports in WebFocus?

This message has been edited. Last edited by: Kerry,

If you are in MRE, then use deferred execution.

Else schedule the report via report caster and use run once immediately option.

This might be helpful: Change timeout settings for IE and IIS

But you might also consider Ram's suggestion to run the report either deferred or scheduled.

Thanks guys. I'm using Managed Reports. I'm new to WebFocus. How do you run Manage Reports as deferred or scheduled?

WebGuy,

Deferred:

In MRE, next to the "Run" icon, you will find the "Run Deferred" Icon.

Choose your report, click on the icon. Your report will be submitted for execution.

Next to the "Run Deferred" Icon, you will find the "Deferred Status" icon. Click on it. You will get a page showing the status of your report. When execution terminates, you will have the options to Delete, View or Save the output.

Scheduled:
Do you have "Report Caster"? If so, you can schedule you report to run at certain predefined times. Check the RC doc.

Thanks deferred/scheduled is good info to know. However, when this reports goes into production it needs to be available to our clients immediately. Isn't there a setting I can adjust that determines when the report times out? I'm not sure if you guys are familiar with Microsoft IIS, but there's a setting on the web server that allows you to set the request timeout...I'm looking for something similiar in webFocus.

I had this problem about a year ago and as Dan Satchell mentioned, changing the timeout settings for Internet Explorer fixed it.

The usual percautions should be taking before dealing with REGEDIT to apply these changes:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
Internet Settings]
Value Name: ReceiveTimeout
Data Type: REG_DWORD (DWORD Value)
Value Data: Time in milliseconds (default = 120,000)

Default seemed to be 60000 (1 minute) - changed to 180,000 - then reboot

Might also be:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
Internet Settings]
Value Name: KeepAliveTimeout
Data Type: REG_DWORD (DWORD Value)
Value Data: Time in milliseconds (default = 120,000)


With that said, you might want to post your code on this forum. Since you are new to WF, you might benefit from having the more experienced WF users make suggestions on how to increase performance.

My question is: Is it timing out in the browser or the reporting server? If the former, how many rows are you trying to bring back? If the latter, what is your CPU time limit for an agent? I think the default is 300 seconds.

I believe it's timing out on report server. Where do I adjust the CPU time limit?

Is report time-out acceptable? How about trying to fix the report so it is more efficiently retrieving the data?

quote:

when this reports goes into production it needs to be available to our clients immediately.

And if the report is taking so long that there is a time-out, regardless of whether it's in the reporting server or in returning the data to the browser, "immediately" is out of the question. Is someone really going to wait three minutes for a report to be returned to a browser? I would go with Francis' suggestion.

The report takes about 6 seconds to load. The older version of this report is already on production and is acceptable to the client.

quote:

a long running sql server stored procedure

So is it long running or 6 seconds? Just trying to find out where the problem lies so we can suggest where to make a change. What's the difference between the older version and this version? How was it changed and why is the change affecting how long it takes to run? (Maybe a parameter is not being passed correctly so it's trying to process/retrieve EVERY record.)

The report is being converted from classic asp to WebFocus but the newer version uses the same stored procedure as the older version. The older version displays a please wait message until the report loads. As I stated before, the newer version will run if I a hard-code the result set in the stored procedure so it can't have anything to do with a missing parameter.

How do you call the stored procedure? How did you create the WebFOCUS metadata for the stored procedure?

Have you read the documentation? Using the Adapter for Microsoft SQL Server