September 26, 2006 at 1:17 am
I am generating reports using SSRS. The report uses a Stored Procedure. The stored procedure executes for about 2-3 hours (Due to huge data and processing) . But when I use web services to generate the report, the Web service timout after few minutes. Can any body guide me to solve this issue efficiently ?
Thanks in Advance
Sandeep
September 26, 2006 at 2:31 am
MyWebService ws = new MyWebService()
ws.TimeOut = time in milli seconds (This value should be set to the approximate SP execution time)
then invoke ws.MyReportFunction(params....)
However you may want to work on optimizing your stored procedure.
Prasad Bhogadi
www.inforaise.com
September 27, 2006 at 4:00 pm
I'd use the sproc to build a permanent table in your database over night. ie pre process the data, then use the report to query the results.
Martin
September 27, 2006 at 10:53 pm
Thanks a lot ! The Web service Timeout concept worked !
If we give the WebService Timeout = -1 , then it is assumed to be infinite timeout.
-Sandeep
February 17, 2009 at 3:54 pm
I am new to this and I also have what I suspect to be a timeout issue - I have a report kicking off a SP and sometimes it takes 20 minutes to run sometimes over 30; when it is over 30 we end up with an error that says:
An error has occurred during report processing.
Cannot read the next data row for the data set [dataset name].
Operation cancelled by user.
How do you increase the timeout as I do not see anywhere to do this? Any help would be greatly appreciated. Thanks ahead.
April 14, 2009 at 2:16 pm
jmichaud (2/17/2009)
I am new to this and I also have what I suspect to be a timeout issue - I have a report kicking off a SP and sometimes it takes 20 minutes to run sometimes over 30; when it is over 30 we end up with an error that says:An error has occurred during report processing.
Cannot read the next data row for the data set [dataset name].
Operation cancelled by user.
How do you increase the timeout as I do not see anywhere to do this? Any help would be greatly appreciated. Thanks ahead.
Just curious, but are you working with any large binary or text values? I've run into this issue before when using ADO .Net to retrieve large values via a DataReader. If I undestand correctly, it has something to do with the buffer used between SQL Server and the client running out of space. The work-around in ADO .Net from a code perspetive is to use the DataReader's GetXXX method to retrieve each column value seperately...
Does that help?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply