I wrote a python program to bulk download ssrs reports.
The program sends a url to the browser to download an SSRS report, which it then renames and moves to specified directory for each key in a dictionary holding parameter values for the report.
For the parameters I've been testing each time I run my program I hit the same SSRS report 63 times.
The problem is that during development, I notice that after a while SSRS stops responding with the error
"The report server execution yhsoj1vs4bjdyqn4c4nw4k55 has expired or cannot be found. (rsExecutionNotFound)".
Then I cannot even manually run the report. The problem usually resolves itself within an hour but how do I prevent this from happening?
It could be the parameters or it could be session timeout or it could be just draining too much of the memory. Is that how it's going to run in production - you hit the same report 63 times? And is that just continually hitting that report? When it stops responding "after awhile" its that with breaks or continually hitting the report?
Have you looked in the Reporting Services log as well as the execution log view in the ReportServer database for other issues, errors when this happens?
Sue
I don't think the parameters that I am passing is the issue because I can pass those same parameters when the report is working without a problem. And the report normally renders very quickly (generally under 5 seconds) since it is based on a very simple query. In production we will need to hit the same report 63 times because as far as I am aware SSRS doesn't have an option to run the same report with multiple parameter selection but to download as distinct files with customized file names on demand. When I say the server "stops responding after a while" I mean that I run my program during development several times successfully but after the 6th or 7th or 10th run for example when I visit the url, I see the "rsExecutionNotFound" error. The number of times I can run my program before the report server stops responding varies. It has stopped responding after just 2 runs, but sometimes I can run my program 20 times before the server stops responding. I checked the Reporting Services log as well as the execution log view in the ReportServer database and nothing seems out of the ordinary.