Link to home
Start Free TrialLog in
Avatar of drivingforce
drivingforceFlag for Afghanistan

asked on

Error "Unable to load client print control" when trying to print in the ASP.NET ReportViewer control

I'm using the ASP.NET ReportViewer control from Microsoft to show reports from the SQL Server Reporting server into a web application on an intranet.

when printed the reports from client machines who have admin priveledges to their own box receive "Unable to load client print control"  

(Note: Working well for some clients who is in same network )


Software-Prompt-1-.jpg
Message-From-Webpage-2-.jpg
Avatar of Andre Thibodeau
Andre Thibodeau
Flag of Canada image

Hello Mr Force.

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 text below into a file with a REG file extension and double-click it...  Best to backup this registry key before deleting it.

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

Andre



Avatar of dave4dl
dave4dl

ASKER CERTIFIED SOLUTION
Avatar of drivingforce
drivingforce
Flag of Afghanistan image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This question has been classified as abandoned and is being closed as part of the Cleanup Program.  See my comment at the end of the question for more details.