**self-hosted organization**
We have a new custom report that has been scheduled to email a pdf to interested parties. The schedule is failing with this error "The report response was null":
This is a new error for me and I see an existing forum post about it occurring on the merge report, but I wonder if anyone has seen it elsewhere?
Ashley Elliott
Database Administrator
St. Louis Symphony Orchestra
314-286-4198
ashleye@slso.org
There are a couple of squirrely SSRS scheduled report errors that can arise related to live to test copies and pushing updates to an existing SSRS report, particularly if there are changes in the parameter set. What I would recommend you do to start is see if you can run the report manually on this instance using the exact same parameters, and then create some new schedules for this report, again with the same parameters as the schedules that are failing. If all of these work, then the easiest (but least satisfying) thing to do is just deprecate the old schedules and recreate them. If they _don't_ work, then this indicates a larger issue with this specific report's configuration, or with your SSRS configuration.
**SOLVED**
This might not work for everyone - I am finding in conversations with others that this error can occur for different reasons. In the SLSO case, we could run the report ad-hoc just fine but the schedule was not working. Turns out that the link to the report broke. Keep in mind we are self-hosted… so, there is a folder in our Report Manager called "Scheduled Reports", and in it are links for all the schedules. As I said, our link broke and I had to point it back to the original .rdl
I hope this helps someone else someday.