I wrote a report in SSRS 2008 R2 last week and published it to a reports library on SharePoint 2010 (SharePoint-integrated Reporting Services). The report worked well, but then the users decided they didn’t want a couple of the parameters. I got back into BIDS and removed the two parameters from every place they occurred, then I tested the report. It worked fine. It worked fine locally, that is, but once I deployed it to SharePoint I found it would not work on the server. The error message was, “One or more parameters required to run the report has not been specified.” The things I did next, I thought I’d list for you, because they might just take care of the problem if this happens to you.
1. Go to the report in BIDS, right-click, and select View Code. There, searching for the word parameter, you may see a left-over reference to the parameters you removed. You can also go to the place you store your SSRS project and inspect the XML for the .rdl and .rsd (dataset) files by opening them in WordPad.
2. Making sure you have the .rdl file safely on your own machine and in your BIDS, go to the SharePoint server and delete the report from the report library before deploying it from BIDS again. I did that, but it did no good at all.
3. FINALLY I tried deploying the report and its datasources and datasets to a new test site on the SharePoint server and the report worked fine. So then I went back to my original site and deleted the datasets that went with this report (they were not needed for other reports, just this one). Then I re-deployed them along with the report and it worked fine on the server.
What was my problem then? The problem was the one or more of my datasets must have had references to the deleted parameters, although I really didn’t think they’d ever used the parameters. I did have the properties of that project in BIDS set so that Overwrite Datasets is True, but I guess since all I did was deploy the report itself the datasets weren’t overwritten because I didn’t specify that they be re-deployed. Moral of the story – redeploy your datasets as well as the report itself if you do some major surgery in SSRS!
{ 4 comments }
Sometimes, the errors encountered in processing are not easily identified. A thorough analysis can solve it, though, wasting a lot of time. The experience of hunting down a error is sexy for some and hellish for many. Thanks for providing an overview of the problem and steps involved in resolving it.
Tottaly agree, but when you come to dead end you have to go step by step. I write it down on a peace of paper what is wrong, and possibilities to solve the problem. Otherwise ask google or ask it on forum. Internet knows ewerything.
Things turn out best for the people who make the best out of the way things turn out.
Everyone have 50% of control of his pure luck!