Ultimate solution (works in SSRS 2012 too!)
Append the following script to "C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportManager\js\ReportingServices.js" (on the SSRS Server):
function pageLoad() {
var element = document.getElementById("ctl31_ctl10");
if (element)
{
element.style.overflow = "visible";
}
}
Actually I don't know if the div's name is always ctl31_ctl10: in my case it is (instead over SQL Server 2012 azzlak found ctl32_ctl09).
If this solution doesn't work, look at the HTML from your browser to see if the script has worked properly changing the overflow:auto property to overflow:visible.
Solution for ReportViewer control
Insert this style line into the .aspx page (or into a linked .css file, if available):
#reportViewer_ctl09 {
overflow:visible !important;
}
Reason
Chrome and Safari render overflow:auto in different way respect to Internet Explorer.
SSRS HTML is QuirksMode HTML and depends on IE 5.5 bugs. Non-IE
browsers don't have the IE quirksmode and therefore render the HTML
correctly
The HTML page produced by SSRS 2008 R2 reports contain a div which has overflow:auto style, and it turns report into an invisible report.
<div id="ctl31_ctl10" style="height:100%;width:100%;overflow:auto;position:relative;">
...</div>
Changing manually (using Chrome's debug window) final HTML overflow:auto in overflow:visible i can see reports on Chrome.
I love Tim's solution; it's easy and working.
But there is still a problem: Any time the user change parameters (my reports use parameters!) AJAX refreshes the div, the overflow:auto tag is rewritten, and no script changes it.
This technote detail explains what is the problem.
This happens because in a page built with AJAX panels, only the AJAX panels change their state, without refreshing the whole page. Consequently, the OnLoad events you applied on the tag are only fired once: the first time your page loads. After that, changing any of the AJAX panels will not trigger these events anymore.
Mr.einarq suggested me the solution here.
Another option is to rename your function to pageLoad.
Any functions with this name will be called automatically by ASP.NET Ajax if it exists on the page, also after each partial update. If you do this you can also remove the onload attribute from the body tag
So I wrote the improved script that is shown in the solution.
Best Answer
What worked for me was in 3 client-side steps :
I could then print even without having to run as admin. Note that I think step #3 is an add-on called "RSClientPrint 2008 Class".
I know this is a very old question, but I had the issue a few times over the years and just now found the solution. I had to try suggestions scattered across multiple sites and could not find a concise solution until I pieced this together.