Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I had the same issue once and found that explicitly specifying what controls in the ReportViewer control should be shown did the trick. I also added a ScriptManager to the page. The code below works in FireFox &amp; Chrome. Also, the ReportViewer control has issues with other browsers when used in conjunction with UpdatePanels. Depending on how your markup is setup, these might be your issues.</p> <pre><code> &lt;rsweb:ReportViewer ID="ReportViewer1" runat="server" Font-Names="Verdana" Font-Size="8pt" InteractiveDeviceInfos="(Collection)" ProcessingMode="Remote" WaitMessageFont-Names="Verdana" WaitMessageFont-Size="14pt" ShowExportControls="true" Width="1280px" Height="700px" ShowBackButton="true" ShowToolBar="true" ShowParameterPrompts="true" ShowPageNavigationControls="true" ZoomMode="Percent" ZoomPercent="100" ShowReportBody="true" InternalBorderStyle="Solid"&gt; &lt;/rsweb:ReportViewer&gt; </code></pre> <p>Some issues such as ActiveX occur with older versions of the reporting controls. You can find out which version by looking in the web.config file. Version 8 and lower have this issue.</p> <pre><code> &lt;add assembly="Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" /&gt; &lt;add assembly="Microsoft.ReportViewer.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" /&gt; </code></pre> <p>Workarounds can be found here: <a href="https://stackoverflow.com/questions/340151/reportviewer-client-print-control-unable-to-load-client-print-control">ReportViewer Client Print Control “Unable to load client print control”?</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload