“Unable to load client print control” in Reporting Services 2005

The user gets a dialog stating “Unable to load client print control” when clicking the print button on a Reporting Services 2005 report.

There much written about this and what Microsoft update broke this so I won’t repeat it here. (Google – reporting services “Unable to load client print control”)

The bottom line is that there’s an update that added a “kill-bit” associated to the ActiveX printing control used by Reporting Services. There’s an update to Reporting Services that supposedly fixes this http://www.microsoft.com/downloads/details.aspx?FamilyID=82833f27-081d-4b72-83ef-2836360a904d&DisplayLang=en

OR you can uninstall these 2 updates KB956803 & KB956391

OR you can just delete the registry entry causing the problem
Copy the red text below into a file with a REG file extension and double-click it

Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{FA91DF8D-53AB-455D-AB20-F2F023E498D3}]

Advertisements

SQL 2008 RTM – SSRS 2008

SQL Server 2008 is RTM this week! Check out this comparison of SQL Server Reporting Services 2008 and 2005. Looks impressive!

Scaling Up Reporting Services 2008 vs. Reporting Services 2005: Lessons Learned

Reporting Services 2005 in a MOSS Site

I wanted to run Reporting Services 2005 reports on my secure MOSS site so the user wouldn’t have to login twice. I did this by adding the Reports and ReportServer virtual directories to my MOSS site in IIS. The MOSS web server had an instance of Reporting Services running on it.

The Reports virtual directory is something like this
C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\ReportManager

The ReportServer virtual directory is something like this
C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\ReportServer

Both virtual directories need to have an “application” created in IIS and should use the same application pool that the MOSS web site uses.

Reporting Services IIS Settings

Now go to the Reports directory and modify the web.config file
The <sessionState> entry should be changed to this
<sessionState mode=”InProc” cookieless=”false” timeout=”20″ partitionResolverType=””/>

Also add the following to the <appSettings> section
<remove key=”ReportViewerMessages” />

Now go to the Reports directory and modify the RSWebApplication.config file
Look for the  <ReportServerUrl></ReportServerUrl> tags and add the URL to the virtual directory
If your MOSS site is http://www.mymoss.com then you would enter http://www.mymoss.com/reportserver
<ReportServerUrl>http://www.mymoss.com/reportserver</ReportServerUrl>

Find this tag  <ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>
and change it to  <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
(Remove the “ReportServer” in the tag)

If you’re using the ReportServer virtual directory to render reports, you will probably also want to modify the web.config by adding this just after the </httpHandlers>
    <httpModules>
      <remove name=”PublishingHttpModule” />
    </httpModules>

This will get rid of the annoying Event Log message. See my post here for more info.