OK, this was a problem plaguing me all day. I created a new report in a project that already had several. Whenever I previewed the report, I continually got the error referenced in the subject line. Howver, what seemed odd was that the file referenced in the Error Window was a totally separate report; one in the same project, but not the one I was working on. I was dissecting my new report to the marrow unsuccessfully trying to find what on Earth in the Parameter was referencing this other report, especially as I had not linked the two in any way. I was getting ready to pull out what remains of my hair, when I consulted with a co-worker who told me that SSRS would check for errors in all reports in the project when previewing any one of them. Is this true? That can be very annoying, if so. I mean, if I have several reports that I'm working on simultaneously, some - heck, maybe even ALL - may have errors that I just haven't gotten to, yet. But, I'm not interested in seeing them, if I'm working on something totally unrelated. If this is the way it works, is there a switch or setting somewhere that can be toggled telling SSRS to ONLY return errors that belong to the active report? If there is no such switch or setting, should I just design all my reports in Report Builder and only use SSRS to gather them all into one project? Oi...

HI Adam ! Are you using TFS as well, usually when you use TFS with BIDS or VS, it tries to build whole project. You might need to remove "Read Only" check from your Project "DebugLocal" or "Debug" folder. Have a look at below article; http://sqljoe.wordpress.com/2011/06/08/ssrs-error-report-preview-displays-access-to-the-path-binreport-rdl-is-denied/ There is no such limitation when you are building reports through BIDS if you have errors in other reports you will still be able to run the reports in your BIDS development environment. Please let me know if this helps. Hopefully i have answered you correctly. Thanks, Hasham

HI Adam ! Are you using TFS as well, usually when you use TFS with BIDS or VS, it tries to build whole project. You might need to remove "Read Only" check from your Project "DebugLocal" or "Debug" folder. Have a look at below article; http://sqljoe.wordpress.com/2011/06/08/ssrs-error-report-preview-displays-access-to-the-path-binreport-rdl-is-denied/ There is no such limitation when you are building reports through BIDS if you have errors in other reports you will still be able to run the reports in your BIDS development environment. Please let me know if this helps. Hopefully i have answered you correctly. Thanks, Hasham

"TFS"? I'm going to venture that I'm not using this, since I do not know what the acronym stands for. I did a search on it and got mostly "Team Foundation Server," which I've never heard of. I'm guessing "VS" is for Visual Studio, which is the main tool I'm using. The report causing a problem was one still in development, but had been put on hold, so there is no effort being made at this time to correct its errors. I removed it from the project - I can work on it in Report Builder at some later time - and the problem went away. Essentially, I have a project with Reports A, B, C and D. Report B is dormant, but not cleaned up; it has problems. I'm working on Report D, but when I preview it, the error window shows the errors from Report B, even though Report D has no relationship with B, other than being in the same project. The current report, report D, is showing no errors and is working fine, but I'm not interested in seeing the errors associated with report B at this time. So, I removed report B from the project, but left the rdl in the project folder so that, when I return to it, I can just add it to the project again at that time. This seems clunky, but all I could think of. I just wondered if there was some toggle I could manipulate to tell the project to only return errors related to the active report, but I'm guessing that there is no such animal.