Cannot Print SSRS 2005 report after installing KB956391

Question

Installed updates on clients yesterday and am now unable to print reports created in SSRS 2005 from Win XP SP2 machine.

When viewing a report selecting the print icon on the report generates a Windows Internet Explorer message box with the text, "Unable to load print control".

After some trial and error, I determined that the removal of KB956391 (The ActiveX Kill Bit update) allows the client to regain the ability to print reports in SSRS 2005. Re-installing the KB again causes the report print to fail.

Ideas anyone?

Answer 1

I've got the same problem at all my customer sites after installing KB956391. I called Microsoft yesterday and they had no clue about the problem. This must affect RS users worldwide now.

 

Answer 2

You should install SP1 of the Report Viewer control which contains a new version of the Print ActiveX Control. Here is the download page: http://www.microsoft.com/downloads/details.aspx?FamilyID=82833f27-081d-4b72-83ef-2836360a904d&DisplayLang=en. You can also just get the CAB file, which is part of the installation and install it 'manually' on the client. 

 

Alex.

 

Answer 3

Does the Report Viewer Control SP1 also include the HTML version of the Report Viewer?

 

Also, which CAB file do we need to update the client PC?

Answer 4

Thanks for the suggestions Alex, however installing SP1 of the Report Viewer control didn't seem to correct anything.  Seems like Microsoft needs to do something to correct this.  I can't expect everyone who accesses our website to have the technical expertise to install activex controls manually, and I really hate to suggest having them uninstall a windows update, although that might be my only option for now, until Microsoft corrects it.

 

Answer 5

1)      Here is the description of what is included from the download page: “The Microsoft Report Viewer Redistributable 2005 Service Pack 1 package includes Windows Forms and ASP.NET Web server controls for viewing reports designed using Microsoft reporting technology.”

 

2)      You do not need to install the new ActiveX Print control manually. You need to upgrade your servers and the customers will be prompted to install a new ActiveX control automatically. For example, if you are using ASP.NET version of the Report Viewer control, you need to update all your Web servers with a new version of the viewer control and also the CAB file which contains the Print ActiveX control. After upgrading both of those your customers will automatically be prompted to install a new version from the CAB file.

Let me know if that was helpful!

Alex.

Answer 6

Thank you, this fixed the problem. Are you able to tell me if this update works for SQL 2000 version of Reporting Services as well?

Answer 7

Thanks again for your response Alex.  The problem I have though is that the report viewer control is embedded in a dotnetnuke module on our website, so I don't have the capability of updating that control.  I imagine I will have to have the company from which I purchased the module create an updated version of their product using the new version of the report viewer control, but I doubt that will happen very quickly.  Any other ideas?

 

Answer 8

Alex,

 

Can you explain #2?  I have installed the MS Report Viewer Redistributable 2005 SP 1 on the sql reporting server but the clients are still getting the printing error message.  They are not being prompted to install an updated cab file and they are administrators on their computers. 

 

Any help would be greatly appreciated.

 

Jacob M.

 

 

Answer 9

Hi all

 

We started to get the "unable to load client print control" after windows update on our server.

And after I installed  MS Report Viewer Redistributable 2005 SP 1 on the server and rebooted the server. The client side could get the pop-up window to let us install it. But when I click "install" button, after a while it still gives me "unable to load client print control" again. BTW My windows login's right is administrator.

Answer 10

I'm getting the same problem as pumaken68.

After installing windows updates on my dev machine (XP SP3) I have experienced the same issues as everyone else. Anyone stil running XP SP2 who did not install lastnights updates seem to be able to print ok.

Have installed the ReportViewer SP1 redistributable on our dev server. Simply ran ReportViewer.exe. Does this include the CAB update btw?

When I run a report using the ASP.NET ReportViewer (from my local machine - connected to the dev server ssrs) I get prompted now for the new ActiveX print control when clicking Print.

I click the install button but after a short wait I then get the 'Unable to load client print control' error again.

Have tried closing all instance of IE, rebooting but still get error. I keep getting promted to install the new ActiveX.

Need a solution to this ASAP if anyone can help. Thanks.

Answer 11

Uninstalling the KB is the only fix I've found for this so far.

Answer 12

 

I did the same and all is OK now. Uninstall KB956391.

Answer 13

Unfortunately we have hundreds of companies with thousands of users running off our live web app and getting them all to uninstall the KB is a no go.

Answer 14

I tried all suggestions and the only thing that worked for me was uninstalling the update.

Answer 15

We cannot get the control to print even when uninstalling the KB update.

Answer 16

I can confirm that we have the same issue. Removing KB956391 and rebooting the PC resolves the error "unable to load client print control" on SQL Reporting Services 2005.

 

We use WSUS 3 to deploy all updates to around 60 PCs automatically. Annoyingly KB956391 doesn't support uninstall by WSUS so it will have to removed from each PC manually.

 

Please post if anyone finds another solution...

 

Ta!

Answer 17

I'm having the same issue and I've tried upgrading the reportviewer control, I've noticed that the controls files don't update when I run the upgrade.. I don't notice any files getting updated with the ReportViewer control upgrade.

Answer 18

The patch set the kill bit for the ActiveX control.  Removing this entry will allow the control to load and user to print.  I am not sure what the ramifications of this are other than they allow users to print.

 

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

 

Looks like Microsoft forgot to put the phoenix entry in the key.

 

Answer 19

I'm in the same boat as Jamiegs.  Perhaps if we could just get our hands on this new .CAB file?  Does anyone have access to the file?

Answer 20

Please note that we have only tried this on a test server and haven't checked all consequences yet, but after installing KB956391 (and getting the "unable to load client print control" error) we noticed that the registry was automatically updated with the following ActiveX clsid (with the killbit set)

 

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

"Compatibility Flags"=dword:00000400

 

We removed the update which subsequently removed this clsid and users were able to print again.

 

The following link provides details of how to prevent RSClientPrint from running in IE (by creating the above clsid), and we followed the instruction under the How to undo the workaround heading (see under the workaround section for  GDI+ BMP Integer Overflow Vulnerability - CVE-2008-3015 section in the Vulnerability Information section of the bulletin). This seems to resolve the problem without having to remove the update.

 

http://www.microsoft.com/technet/security/bulletin/ms08-052.mspx 

 

We also checked the following link which details how to stop ActiveX controls running in IE. It mentions an AlternateCLSID that can be set when a new version of an ActiveX control is installed. We are assuming that we have to do this after installing SP1 of the Report Viewer control as we understand that this loads a new version of the Print ActiveX Control (with a new clsid we assume). We don't know this yet as we haven't loaded SP1 (it may create the AlternateCLSID value automatically).

 

http://support.microsoft.com/kb/240797

 

Again, please note we are doing this on a test server so it's not a problem for us if we come across any further issues doing the above.

 

Anyway, apologies for the long and winding post, but hopefully this helps.... 

Answer 21

You can also turn the killbit off in the registry, which is probably a better temporary solution then uninstalling the update because you'll still be protected from the other vulnerabilities that the update addresses and it would be easier to automate, since you could do it thru the group policy.

 

Code Snippet

Windows Registry Editor Version 5.00

 

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

"Compatibility Flags"=-

 

 

 

 

 

 

Answer 22

The update is the culprit.  Instead of having to do a massive work around, why can't Microsoft just fix their update?  I uninstalled the KB from my machine and told my users to do the same.  Having to tweak the registry or jump through any hoops because of bad coding is unacceptable.  Fix the update.

Answer 23

Well, Microsoft actually meant to kill the report viewer because it has a vulnerability that will allow Remote Code execution.

The update is doing things correctly.

By removing the update you're making yourself vulnerable.

Microsoft needs to release an update to the report viewer control, or to GDI+, which is what actually contains the vulnerability, to remove the vulnerability, then another killbit update to turn the control back on. 

By turning off the killbit you would open up the vulnerability again.

Idealy Microsoft would've fixed the controls before setting the killbit, but that takes time and the remote code execution hole would be out there until it got fixed.

But some people can't wait for it to be fixed, since our clients need to print their reports.

I know most people want their stuff to work, but more so I don't want hackers running things on my computer.

Answer 24

Interestingly enough, this same problem started today at our office, but nobody can find KB956391 on anybody's machines, nor do I see the aforementioned registry value.  Is anybody else in my boat?

Answer 25

cousinduck : Have you tried to look in the %windir% folder? There should be a hidden folder named $NTUninstallKB956391$, browse through it and you'll end up finding a file called "spuninst.exe".

 

 

Answer 26

I had this problem this morning as well.  The first step I took was the installation of the newest Report Viewer, but this did not resolve my problem.

 

I was able to resolve it by applying the SQL Server patch mentioned in MS08-052

 

http://www.microsoft.com/technet/security/Bulletin/MS08-052.mspx

 

Once this patch was applied, the users were prompted to re-install their Active X control the first time they clicked the print button.

 

My server was 9.0.3042 so the patch I applied was KB954606.

 

Answer 27

DITTO! UNISTALLING KB956391 is the only thing that worked for me.  Now I have to relay these instructions to my helpdesk staff so that my 200+ users can continue to print after they get this same update.  Thanks A LOT!

 

 

Answer 28

SFinnie's suggestion is the way to go.  I installed KB954606 on the server (actually, it was available and waiting via windowsupdate.com) and all is happy now.

Answer 29

Best I can tell is that we don't have this update and we are not getting the same error as what is reported in this thread.  Here is what we are getting.

 

It appears to only be happening on XP PCs.  It happens with SRS 2000 and SRS 2005 reports (on different servers).  The user can view the report fine.  But when the user clicks on the Print icon to print the report to paper, one of the following errors is displayed.  Clicking OK closes IE.

 

Error title:

IEXPLORER.EXE – Application error

-or-

SYsFader: IEXPLORER.EXE – Application error

 

The instruction at “0xff92701a” referenced member at “0xff92701a”.  The memory could not be “read”.

 

Thoughts?

Answer 30

There is some confusion around the Print Control and why it stopped working with the latest Windows update.

 

There was a KillBit released from Internet Explorer to make older versions of the Print Control stop working. This is for a high priority security updated. You can find more details on the update at one of the links below.

 

In order to have a working print control, it depends on where your client is printing from.

 

1. If you are using a Server mode rendering and printing, you need to have updated the Reporting Services server with the GDR for GDI+. This updated can be obtained here: http://www.microsoft.com/technet/security/bulletin/MS08-052.mspx Until that updated is applied, and your client machines have the KillBit patch, you will not be able to print at the client machines. Applying the above mentioned patch on the Report Server is the correct solution.

 

2. If you have a Report Viewer Local Mode application, where you are printing from localmode and not Server mode, you need to install the Report Viewer redist that has the proper fix. http://www.microsoft.com/downloads/details.aspx?FamilyID=82833F27-081D-4B72-83EF-2836360A904D&displaylang=en

 

Applying the Report Viewer redist to a report server does nothing to help clients print.

 

 

 

 

 

 

 

 

Answer 31

We updated our reporting services with MS08-52 and we installed the report viewer redist both on the report server.  We are using server mode rendering and printing.  Since we installed these updates, we now get prompted to install the print control and it does download; however we have a new problem.

 

When the Preview button is clicked, we receive "An error occured trying to render the report. (0x8007F303).  Also when reports are printed (it seems to only be landscape reports), the font specified in the report definition is not what's being used.  The font being used is much wider and therefore throwing off the spacing so that each page takes two pieces of paper.  Everything looks fine on the screen.

 

Any help would be appreciated since our customers have not been able to print for two days now.

Answer 32

 

We found a solution that seems to have worked without any errors encountered in our application. If you apply KB954606 downloaded from here it seems to solve the issue.  We did need to have the user logged in as an administrator in the client trying to print and they have to try printing before the update gets applied but it worked for us.

 

Hope this helps.

 

-Travis DeAngelis

Sr. Software Engineer

AdvancedMD Software

Answer 33

Thanks but we have installed KB954606 and are still having the same issues with the preview and the landscape reports.  Does anyone know what the error in the preview refers to - "An error occured trying to render the report. (0x8007F303)."?

Answer 34

After installing the update on the server (KB954606), clients were able to print reports again.  The update did not require a reboot and we didn't have to stop any services before installing the patch.

 

Thank you guys!

 

 

Etienne St-Georges

Answer 35

 

We are running in Server mode.  Both patches and the killbit have been applied and still nothing.  Also, just for the sake of experimentation, I went and downloaded the most recent report viewer redist.  When you check the knowledge base article, it claims the version that will be installed is: 8.0.50727.1843, but when I install it and check the version of my dlls, they are 8.0.50727.762. 

 

Not sure where to go from here, but, well, Microsoft has really dropped the ball on this one.

Answer 36

Hey Alison Cavano - I had the same problem

 

Try to re-register the RS Print Client files.

 

Browse to your reportserver\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\bin\RSClientPrint.cab

 

Extract the contents into c:\windows\system32

 

Then run regsvr32 rsclientprint.dll /s

 

I just wrote a script to do all this and put it in a GPO to roll this out

 

Batch Script******

COPY "\Print Client files\*.*" "C:\Windows\System32\" /Y

regsvr32 rsclientprint.dll /s

 

 

Answer 37

We are running SQL 2005 SP2 on Windows 2003.

 

We have applied both KB954593 and KB954606.

 

All clients (that have not uninstalled KB956391) still get the 'Unable to load Client Print Control'.

 

Those clients that have uninstalled KB956391 get the prompt when printing, but unfortunatly all reports that have been specified as landscape now default to portrait.  They are also asked to install it each time they print.

 

Anyone have a fix for this?  I'm about to put in a support call.

 

 

Answer 38

Willow_Eric.. I'm in the same boat as you.. although haven't seen the layout problems, or atleast not yet..

I actually already had KB964606 installed on our server before all this happened and what confuses me is that isn't that the update that is supposed to fix this for the clients?

I have installed KB964607 with no luck, uninstalled it, and uninstalled 964606 and then reinstalled 964606.. with no luck.. 

Have also downloaded the updated Report Viewer redist and tried re-registering the rs print client files.. rebooted multiple times.. restarted iis multiple times.. and still nothing.. 

I am also running RS in Sharepoint Integrated Mode but i don't think that has anything to do with it. 

So what am I missing here?

Answer 39

TTZedX -- After speaking with a support tech, manually re-installing the client control CAB fixed the clients.  The clients I've patched can now print from the Report Manager, but from our own application (app that uses the reportviewer control), they still get the same error.

 

I need to keep digging.

 

 

Answer 40

LeeFAR wrote:

Best I can tell is that we don't have this update and we are not getting the same error as what is reported in this thread.  Here is what we are getting.   It appears to only be happening on XP PCs.  It happens with SRS 2000 and SRS 2005 reports (on different servers).  The user can view the report fine.  But when the user clicks on the Print icon to print the report to paper, one of the following errors is displayed.  Clicking OK closes IE.   Error title: IEXPLORER.EXE – Application error -or- SYsFader: IEXPLORER.EXE – Application error   The instruction at “0xff92701a” referenced member at “0xff92701a”.  The memory could not be “read”.   Thoughts?

 

I want to let folks know that our problem has turned out to be a HIPS problem.  We need to deal with this and then worry about what this thread is about.  My guess is Mcafee put out something to address the GDI+ problem, which caused us to go south.

Answer 41

Added KB95406 from MS08-052 to the Reporting Server, and reapplied the KB956391 to the client. Selecting print from a report in Reporting Services now works correctly.

Thank you for the assistance. 

Answer 42

Hi,

We experienced the same issue.

 

It works if you uninstall both KB956391 and KB956390.

After you have uninstalled these 2 updates, you might want to run the windows update again as a custom installation, uncheck the two updates and check the mark that ensures you are not asked to install this update again in future updates.

 

BUT there is a security issue regarding killbits in ActiveX's as what you might define ReportClientPrint control as.

 

So still there is no satisfying solution for this issue.

 

Bjorn

Answer 43

I’m posting this to see if this helps anyone.  We have identified the first culprit of this issue.  It looks like HIPS was causing this problem.  We are unsure at this point, but we think McAfee put out a update to prevent a vulnerability as mentioned later in this email.  Another potential problem is that Microsoft released critical security update on Tuesday that has not been deployed yet to us that would have also broken this.  This security update would have instructed IE to not allow the current version of the SRS printer control to be allowed. 

 

All of this is in response to a vulnerability called the Microsoft GDI+ BMP Integer Overflow Vulnerability and appears to have been identified in September.  The SRS printer control uses the gdiplus.dll, which is where the vulnerability exists.  Back in September, Microsoft released some patches for SRS 2000 and 2005 (see these links for the patches) to address the issue the SRS printer control.  The reason for the security update that was released on Tuesday was to prevent the older version of the control from still being used to lessen the exposure of the vulnerability.  My guess is they were betting that people would have applied the patches released back in September before the security update came out on Tuesday.  Late this afternoon, we applied these patches to our development/testing SRS servers to see if the original issue was resolved.

 

I have done some tests and it would appear the patches fixed the problem, however thereis one caveat to this.  The patch that was applied causes a new version of the SRS Client Printer ActiveX control to have to be installed onto the user’s PC.  Based on my tests, the new ActiveX control has to be installed by a high-level account.  Depending on how your browser ActiveX control settings are set and depending on if you are running XP or Vista, you will see things behavior differently.  Chances are, if you are running IE as a LUA user, you are going to either get a JavaScript error in the SRS page or you are going to get some warning that says you do not have the permissions to install the control or you will get an error like “unable to load client print control”.  In any event, this means that you have to browse the report and click on the printer icon using a high-level account.  When you do this you will get the printer dialog window, which is a good thing.  Then if you return as a LUA account and try this, it will work as normal.

 

By the way, it would appear the patch installs the ActiveX control as the “RSClientPrint 2005 Class” (class id = {41861299-EAB2-4DCC-986C-802AE12AC499}) where as before, the one we have been using that has the problem is “RSClientPrint Class” (class id = {FA91DF8D-53AB-455D-AB20-F2F023E498D3}).

 

After we have done a little more testing, we will apply the two patches to our production servers.

 

Answer 44

 

Tried this blog: http://www.technologystudio.net/blog/post/Microsoft-Update-KB956391-breaks-Reporting-Services-ReportViewer.aspx

 

To find the current version of your sql server instance, create a new query use master database and run:

SELECT @@VERSION

GO

 

Bjorn

Answer 45

Willow_Eric wrote:

TTZedX -- After speaking with a support tech, manually re-installing the client control CAB fixed the clients.  The clients I've patched can now print from the Report Manager, but from our own application (app that uses the reportviewer control), they still get the same error.   I need to keep digging.

Willow_Eric..  When you say manually re-installing the print control cab, do you mean that you copied the cab file from the server to each client and re-installed, or downloaded the report viewer redistributable and installed on the clients? 

I have tried both, on clients and servers, and uninstalling the activex control hoping it would prompt me again but so far it hasn't.

Answer 46

I'm still having the issue also, I've updated to the SP2, Installed the GDR update and installed the ReportViewer 2005 SP1 Redist.

I can print from Reporting Services Report manager but not from our application.

We're using ASP.NET 2.0, we're not using 3.5 yet.

Do I need to update the control in my app? With what? How?

Answer 47

Ok, I might have it, but I won't know for sure until late tonight when I publish the changes to our production servers.

 

What I did is extract the ReportViewer SP1 full Redistributable to a folder using a /C switch.

 

Inside a ReportV1.cab file there are *.DLL files that have a later build version then the ones that come with Visual Studio 2005. The files had longer file names like 

FL_Microsoft_ReportViewer_WebForms_dll_117720_____X86.3643236F_FC70_11D3_A536_0090278A1BB8

  but I just renamed them.

 

I replaced the ones that came with Visual Studio 2005 with the newer build and now it works when ran from my computer, where it didn't before I replaced them.

 

I'm going to try it on our test server. I'll let you know what I find out.

 

UPDATE: It didn't work

Answer 48

I've looked into %windir%\setupapi.log & found following (see below)
looks like installation starts & fails for some reason.
Scenario is repoduceble for both WXP SP3 & W2K3 SP2 hosts without KB956391
for WXP SP3 I had KB856903 installed.

removal of KB856903 fixes issue.
after successfull installation of SRS printing ActiveX, both KB856903 & KB956391 could be reinstalled.
Everything will work fine.

Code Snippet

[2008/10/20 10:31:30 6076.1]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_3082.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_3082.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_3082.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:32 6076.2]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_2052.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_2052.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_2052.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:32 6076.3]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1053.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_1053.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1053.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:32 6076.4]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1049.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_1049.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1049.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:32 6076.5]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1046.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_1046.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1046.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:33 6076.6]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1043.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_1043.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1043.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:33 6076.7]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1042.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_1042.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1042.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:33 6076.8]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1041.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_1041.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1041.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:33 6076.9]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1040.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_1040.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1040.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:34 6076.10]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1036.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_1036.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1036.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:34 6076.11]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1033.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_1033.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1033.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:34 6076.12]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1031.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_1031.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1031.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:35 6076.13]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1028.rll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint_1028.rll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint_1028.rll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:35 6076.14]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint.dll" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint.dll".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint.dll" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
[2008/10/20 10:31:35 6076.15]
#-198 Command line processed: "C:\Program Files\Internet Explorer\iexplore.exe"
#-024 Copying file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint.inf" to "C:\WINDOWS\Downloaded Program Files\RSClientPrint.inf".
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\DOCUME~1\ABilyk\LOCALS~1\Temp\1\ICD1.tmp\RSClientPrint.inf" will be installed (Policy=Ignore). Error 87: The parameter is incorrect.

Answer 49

Olexander, do you mean KB956803 rather then KB856803 ?  I wasn't able to find KB856803.

 

Good find, I'm getting the same errors in setupapi.log

 

Did you remove KB856903 from your server or client computers or both?

 

Answer 50

 

I was able to resolve my issue (after applying the patch I could print from the ReportManager, but not my own appilcation) by installing and switching to the ReportViewer 2008 SP1 (I was previously using 2005 SP1).

 

It is version 9.0 -- I removed all references to 8.0 from my app, set a reference to 9.0 and deployed.  I had to install the 2008 distrib. on the server.

 

 

Answer 51

Eric, I did the same thing. but the control seems to no longer work inside VS2005, are you noticing the same thing?

Otherwise it appears to be working fine.

 

 

 

 

Answer 52

The solution that has worked for me so far was to patch the Server with KB954606 which updated the file RSClientPrint.cab, among other things.  Here's the post that clued me in (thanks Jamie):

http://www.technologystudio.net/blog/post/Microsoft-Update-KB956391-breaks-Reporting-Services-ReportViewer.aspx

I also updated the ReportViewer redistributables, but that in itself did not fix the problem, nor did removing the suspect updates from the client (which is not a practical solution in any case given the number of clients involved.)

The problem appears to be, as others have mentioned, that the killbits update to the client assumed that the patch to the server side with the updated control had been broadly applied.  Apparently it had not, which raises some questions

The cab file is located on my test server here and now has a date of 8/5/2008.
D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin

I hope this helps.

Answer 53

Thanks LeeFAR, The problem is sloved.
My SSRS version is 2000SP2, So after I install the KB954609 , all client can print the reports.

So I guess SSRS 2005 is the same way to solve the problem.

Answer 54

By following this forum my half problem got solved,

 

Our web application is displaying SSRS report, and Click on Print, Report is gets printed using RSClientPrint

 

For RSClientPrint, Report Server url and input parameters are passed using Java script.

 

I have installed Security Update for SQL Server 2005 Service Pack 2 (KB954606)

http://www.microsoft.com/downloads/details.aspx?familyid=4603C722-2468-4ADB-B945-2ED0458B8F47&displaylang=en

 

Old ActiveX was “RSClientPrint Class” class id = {FA91DF8D-53AB-455D-AB20-F2F023E498D3}.

 

After installing patch new ActiveX named as the “RSClientPrint 2005 Class” (class id = {41861299-EAB2-4DCC-986C-802AE12AC499}) got installed.

 

Still it was not working.

Then I found that our ASPX web page , we have hardcoded Object id of RsClientPrint, We have changed to new ActiveX id.

After that We are able to print Report in web server.

 

But on client machine, Problem still exists, Client has Administrator Permissions on his machine.

He is not getting ActiveX installation prompt.

 

Can any one suggest Solution for this.

Answer 55

I had the same problem

Tracked it down to the print control config file assembly version reference.

(~Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\ReportingServicesService.exe.config)

 

The assembly reference in the config file was:

   <dependentAssembly>
    <assemblyIdentity name="Microsoft.ReportingServices.Interfaces"
        publicKeyToken="89845dcd8080cc91"
        culture="neutral" />
    <bindingRedirect oldVersion="8.0.242.0"
       newVersion="9.0.242.0"/>
   </dependentAssembly

 

The version in the new cab file is 9.0.3282.0 so I changed the assembly reference.

The client machines now prompt & download the new cab file and reports print correctly.

 

 

 

Answer 56

This is my situation:

 

1. had a working machine

2. installed the KB856903 bad patch so the print ctrl didn't load.

3. installed the latest version of the report viewer ctrl

4. installed KB954606

 

The print control would load from report server but not through our website.

 

5. modified ReportingServicesService.exe.config as per A Diserens post.

6. restarted the reporting services service.

 

control would still not load through our website.

 

7. restarted IIS

 

the print control loaded! (without prompt to load new ctrl)

 

8. got some uses to test

 

you guessed it - print control failed to load.

 

any help very greatfully received.

 

 

 

 

 

 

 

Answer 57

I am able to solve issue

1. I have installed SQL server SP2 update KB954606 on web server.
2. In Web site ASPX page, i have changed Object Id field of RSPrintClient , Given new RSPrintClient Id and in Code base given url of Website.

<OBJECT ID="RSClientPrint" CLASSID="41861299-EAB2-4DCC-986C-802AE12AC499"

CODEBASE="<Location .CabFile Located>rsclientprint.cab#Version=2005,90,3073,00" ></OBJECT>

3. search for RSClientPrint.cab file in Webserver (It get downloaded with SQL server updates). Check registry for New RSPrintClient Id. in web server machine.
4. Copied new RSClientPrint.cab file to my Website Virtual Folder.
5. changed IE Setting in Client machine to allow download ActiveX control.

When client browse website, He  gets prompt to install ActiveX control.

Now I am able to print @ Web server and all client machines

Answer 58

Updated sticky with answer

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=4038102&SiteID=1

 

Answer 59

I found the solution for this.

 

1 Install KB 954606 at sql server  IF you have SQL Server 2005 SP2 9.3042 - 9.3072

2 Install KB 938464 at server IF you have sql server at OS window server 2003 SP2 (any Standard or enterprise Edition) 

3 Install Report viewer Distributable 2005 SP1 at same server. You will find all this thing to download at below mentioned link

 

http://www.microsoft.com/technet/security/Bulletin/MS08-052.mspx

 

4 Go to the services (Run services.msc) on same server and stop the IIS services 

5 Just take care when you stop services there are three more service they will also stop with IIS.

6 Start IIS services and all attached services which stoped with IIS(HTTP SSL,WWW, IIS).

   Or you can reboot the server.

 

You dont need to da anything on client machine.After this, may be some client find Error "Error Loading Resource Library (0X8007007E) when they client print icon, Then please register the RSClientprint.dll(RSClinetPrintclass 2005) By command prompt using command "regsvr32 RSClientprint.dll"

 

Then try at the client machine and server too. Hope this will help you guys.

 

Enjoy!!!

 

Ash

 

 

 

 

Answer 60

Jamiegs:

Did you get your reportviewer controls to work in VS2005?

I used some custom security in my C# apps and all of mine were broken too. It looks like applying the 954606 patch changed the  directorysecurity settings on my ReportServer. You might want to check that.

Hope that helps.

Answer 61

Has there ever been an official fix from Microsoft for this?

Answer 62

 

DebugDiva - can you tell us which settings where changed?  What did you do to fix it? 

 

Thanks,

-Lukasz

Answer 63

If you read Brad's post earlier, He suggested reading the article below.

http://www.microsoft.com/technet/security/bulletin/MS08-052.mspx

This article was just updated for this Reporting Services issue. It explains to install the 'Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies'. This was just updated. It does not have a new version in the title, but it is newer than the version I downloaded previously. I installed it last night and it worked right away. The clients needed no change at all. I am not positive if I rebooted the server or reset IIS (Sorry guys...). I had employees test this from their computer today and they were not even prompted for anything. The print control just worked for them!

http://www.microsoft.com/downloads/details.aspx?familyid=1E53F882-0C16-4847-B331-132274AE8C84

I hope this helps others!

Answer 64

 

Hi, i have the same problem, yes it works after uninstall the KB956391,

but i don't think this is a correct solution.

because it will affect all my clients machine.

Does microsoft have any idea? or coming any solution to fixed this updates?

 

Does this is mandatory updates or optional?

Anybody can answer me?

Answer 65

 

The report viewer solution works but I found out that the Reporting Services MUST be 9.00.3073 or 9.00.3282 and higher. I've tested it and confirmed that. With RS on 9.00.3233 I would still get the same error. Only after upgrading RS it allowed client to download new, fixed activeX print controll and all worked fine.

 

Hope this helps.

Answer 66

I've installed on my webserver the Microsoft Report Viewer Redistributable 2005 SP1 (Full Installation)

Link to download : http://www.microsoft.com/downloads/details.aspx?familyid=E7D661BA-DC95-4EB3-8916-3E31340DDC2C&displaylang=en

 

and it work fine work.

 

Answer 67

Brian Hartman’s blog spells out in a clear manner (unlike MS08-052) what you need to do to fix this problem. It definitely worked for me. Here’s the link

 

http://blogs.msdn.com/brianhartman/archive/2008/11/05/client-print-fails-to-load-after-microsoft-update-956391.aspx

Answer 68

We had the same problem and it was resolved after installing SQL Server 2005 CU9.

Answer 69

Adding the update also corrected my environment as well.

---

-- Jonathan Kehayias (MCITP) | Please mark answers that solve your problem | http://www.sqlclr.net

Answer 70

Eric Cygnus B2B said:

The patch set the kill bit for the ActiveX control.  Removing this entry will allow the control to load and user to print.  I am not sure what the ramifications of this are other than they allow users to print.

 

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

 

Looks like Microsoft forgot to put the phoenix entry in the key.

 

I've change the value in the key "Compatibility Flags" from "1024" to "0", seem like it works, because id show the select printer dialog insteld of Error dialog.

Answer 71

How does one go about uninstalling the patch? I don't see it listed in the Add/Remove programs list

Answer 72

 

If you are running an unpatched SQL Server or VS, you are probably using the print control that was disabled by a recent security update.  Patching SQL Server and Visual Studio should address the problem.  Details are available here: http://blogs.msdn.com/brianhartman/archive/2008/11/05/client-print-fails-to-load-after-microsoft-update-956391.aspx

Answer 73

The root cause of this issue is that when printing from RS, an ActiveX control for print function is downloaded to the client. but after apply the kb, the old version of the control is killed. so the action plan is to install cu9 for RS mgr, or install rptvwr control new redistributable.

not every bi software needs to download activeX, cause it adds the load of the network.

Answer 74

I ran option 2 on both my local machine (XP with VS.net 2008) and the 2k3 server

I get the correct version finally; but installing activeX control errors Windows XP running IE8 (not beta) and get an application error on the install

iexplorer.exe

the instruction at 0x06970068 referenced memory at 0x06970068 the memory could not be written

Not exactly sure what is going on but this is hurting trying to search to resolve this issue ....

Answer 75

Hi,
I’ve tried this accepted solution, and it does not work for me.  We are running the SRS output in Server mode on an x64 WIN2K3 Server and I installed the patch found in bulletin MS08-052.  My client side still did not print. 

I made sure that my IE settings were correct as found here:  http://msdn.microsoft.com/en-us/library/ms159190(SQL.90).aspx and here: 

http://msdn.microsoft.com/en-us/library/ms155874(SQL.90).aspx.

After exhausting all feasible solutions short of uninstalling KB956391 , I decided to uninstall KB956391 .  After taking this step, I was able to print.

I cannot ask my clients IT staff to do this.  Many of our clients are Bank, and there is no way they will uninstall a Critical KB.  I would not even ask them to do so.

So, what do I do next?  Does anyone else have a solution?  Is Microsoft working on a solution?
Thanks.

Answer 76

hi, pjordan29,

please try this following steps:

Problem:

Unable to load client print control.

 

Cause:

This issue is seen when KB 956391 has been installed on the client.

 

Microsoft Security Advisory: Cumulative security update for ActiveX

http://support.microsoft.com/?id=956391

 

This update killbits an older version of the RSClientPrint, due a vulnerability on it.

But for this update to work the report server must have been patched as well and perhaps also the ReportViewer control has to be updated.

 

You should leave KB956391 installed on the client machines and then check the below.

 

Resolution:

First check the report server version.

It must be 9.00.3073 or 9.00.3282.

 

If not, update the report server:

 

Security Update for SQL Server 2005 Service Pack 2 (KB954607)

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5148b887-f323-4adb-9721-61e1c0cfd213

 

 

Now check the version of the ReportViewer control.

You do this by having the customer open a report for viewing on a client machine.

Then have them right click on the report and select “View Source”.

 

Locate the line that looks like this:

 

<script src="/TestRSClientPrintReportViewer/Reserved.ReportViewerWebControl.axd?OpType=Resource&amp;Version=X.Y.ZZZZ

 

Now, if the control type is “Reserved.ReportViewerWebPart.axd” then this is an issue with SharePoint.

The “Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies” has been updated to work with the new rsclientprint.dll. 

Download center link:

http://www.microsoft.com/downloads/details.aspx?FamilyID=1e53f882-0c16-4847-b331-132274ae8c84&displaylang=en

 

 

If the control type is “Reserved.ReportViewerWebControl.axd” we should check the following:

We have 2 different major versions here: 8.00.50727 and 9.00.XXXX.

If you see version 8.00.50727 this means you are browsing reports from within CRM or using the ReportViewer control in a custom 2005 web application.

If you see version 8.00.50727 and the version is earlier than 8.00.50727.1843 then you should install the below on the ReportServer or on the CRM server:

 

Microsoft Report Viewer Redistributable 2005 Service Pack 1

http://www.microsoft.com/downloads/details.aspx?familyid=82833F27-081D-4B72-83EF-2836360A904D&displaylang=en

 

If you see version 9.00.XXXX or 9.0.XXXX then you are browsing through Report Manager, Report Server or perhaps a customer web application built with VS 2008.

Then you should install the below on the report server:

 

Microsoft Report Viewer 2008 SP1 Redistributable

http://www.microsoft.com/downloads/details.aspx?FamilyID=bb196d5d-76c2-4a0e-9458-267d22b6aac6&DisplayLang=en

 

This will bring you up to version 9.0.30729.1 for the ReportViewer control.

 

After having updated the ReportViewer control you must issue an iisreset command so that the updated controls will take effect.

Answer 77

this is not a good idea to remove the kb. but it can be a workaround.

Answer 78

I am having this problem and it's a real killer cause I can not find any solution at all. Since 5 days ago I am getting this ugly message that the control can not be loaded.

I don't have KB 956391 installed. Honestly I am not really sure where to look for it either cause it can not be found in the Add/Remove Programs. Another thing is that my Reporting Server version is 9.00.4220.00 and the database is kept on a different X64 computer. Installing an older fix for a newer version would probably not be such a good idea :(

Any other idea please ?

Answer 79

Thank you for your post Peng.   It was the solution.
I found that just installing the Microsoft Report Viewer Redistributable 2005 Service Pack 1 solved the issue.