January 10, 2010 at 11:14 am
All,
I've run into an issue with one of the SSRS reports that we are generating. Recently we have had to make some changes that cause the report to take longer to run. Here is how the report is set up:
Report has two parameters: one is a datetime, the other is a string based off of a SQL Server sproc. There are two other data sources that are queried when the report is run: on is a sproc that takes less than a second to query, the other is a web service that takes 4-6 minutes to return. If the report takes less than 5 minutes to run everything works just dandy.
The problem is the that when that after the web service returns after 5 or more minutes I get odd results. With the report running for just about 5 minutes I will get an error on my text boxes that have expressions on then that states:
[rsRuntimeErrorInExpression] The Value expression for the textrun ‘AccountValue.Paragraphs[0].TextRuns[0]’ contains an error: Object '[xxxx].rem' has been disconnected or does not exist at the server.
When I get this error, if I go to the next page in the report it will display the data just fine. If I go back to the first page of the report it will also pull the data just fine.
When the report runs for 6 minutes or longer I will get a hard error where the report doesn't render at all that states:
Object '[xxxx].rem' has been disconnected or does not exist at the server.
When running the web service call via IE / Firefox it will work just fine regardless of how long it takes to run. My guess is that it is related to how SSRS is handling the timeouts of the web service or how IE is handling the connection state between SSRS and the web service. Is this the correct path? If so where do I change these settings?
I've already verified that the timeouts on the datasets/sources withing the report are set to 900 seconds (15 minutes) and also have set the httpRuntime executionTimeout option in the webservices web.config file to 900 seconds.
Thanks in advance for any responses.
January 24, 2010 at 4:07 am
I have the same problem.Could you solve the problem?Please let me know if you have found solution.
Thanks
January 27, 2010 at 7:34 am
I can't be 100% sure because I pretty much lost my mind trying to figure this out but I think this only effects the development studio. If you can, upload the report onto one of your reporting servers and verify that you still get the error.
My long term solution was to create a CLR function within SQL and then use a SQL stored proc to call the CLR function and return data to the report.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply