Hello,
I chased an error with the same error message recently thinking it was a timeout issue, only to find out that although the query for the report worked famously for months, it turned out it was because a end-user entered a record omitting a field that was used for a calculated output field in the dataset.
The error you are receiving for a timeout often shows the very same way when Null values are not accounted for in the query seeming like it is timing out. This can happen because the query will run all the way up to the point where it does the calc and stop on the single record that may be null.
I revisited the query and included the ISNULL() SQL function on any field that required the calc and it immediately corrected the issue.
Main Topics
Browse All Topics
by: zephyr_hexPosted on 2009-06-23 at 11:12:41ID: 24694385
ha. had this error myself this morning... and for whatever reason, it resolved itself.
however... i do have a suggestion which may server as a "work around" for you...
in reporting services, you can cache your reports. have you considered using caching? this will reduce the load, and reduce the chances of timeout.
even for troubleshooting purposes, this may be helpful. you could enable caching on the report (say.. 30 min cache), run the report from the report server in order to create the initial cache... and then run the report through the report viewer web part. the report should come up immediately, as it is using the cached copy you just created and not actually querying the data source.
if that doesn't resolve your issue, i recommend that you check SQL logs to see if indeed a timeout or some other error is being reported.