Solution and explanation - Report printing issues for the GDI GDR security update - KB956391.

Question

 

Four situations to understand regarding the security update, the Active X print control and printing using the stand alone Report Viewer.

KB956391 has a Killbit for older versions of the RSClientPrint control due to a security vulnerability in another product (GDI+.dll), which some versions of the Active X print control were associated with.

1. Server mode and printing. Last month, a Microsoft Update patch with the GDR and CU patch for Reporting Services were released for updating the Reporting Services server. You can find information and get details here: http://www.microsoft.com/technet/security/Bulletin/MS08-052.mspx Please note: If you are using your own Web Service for your server mode Report Viewer report with Active X print, you will need to install the latest redist in the link below on the web server.

If you do not patch your server and your clients do get patched with the Killbit, then you will not be able to print. Patching the server is the recommended solution.

2. Local mode and printing. Concurrently, we released an updated Report Viewer Redist. You can find the redist here: http://www.microsoft.com/downloads/details.aspx?FamilyID=bb196d5d-76c2-4a0e-9458-267d22b6aac6&DisplayLang=en

 

3. Sharepoint integration. The Reporting Services Sharepoint add-in needs to be udpated in order to print. The patch is now available at: http://www.microsoft.com/downloads/details.aspx?FamilyID=1E53F882-0C16-4847-B331-132274AE8C84&displaylang=en

 

4. Invoking the client print control in java script or your own code. As part of the security update, the CLSID associate with the control was changed. The application will need to use the updated CLSID. The ID can be found on a machine where the new print control is installed in the in file: \windows\downloaded program files\rsclientprint.inf  Different versions of the control use different CLSID. Here is the updated list.

Product	Architecture	CLSID
RS 2000	X86	41861299-EAB2-4DCC-986C-802AE12AC499
RS 2005	X86	41861299-EAB2-4DCC-986C-802AE12AC499
RS 2008	X86	5554DCB0-700B-498D-9B58-4E40E5814405
RS 2008	X64	60677965-AB8B-464f-9B04-4BA871A2F17F
RS 2008	Ia64	60677965-AB8B-464f-9B04-4BA871A2F17F

 

Microsoft update has all of the Report Server and Report Viewer patches ready to download and install. Applying the Microsoft Update to both the server and clients will fix the problem.

****Reporting Services 2008 is not part of this security update****

If you are seeing issues you cannot solve, email me directly with a repro.  [e-mail]

Answer 1

I clicked on the link in item #1 (Server Mode and Printing). I scroll down the page and click on the link for SQL Server 2005 SP 2 (KB954606). I am then directed to the following page:

 

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

 

How do I know which of these three files to download?

 

SQLServer2005-KB954606-IA64-ENU.exe	55.7 MB
SQLServer2005-KB954606-x64-ENU.exe	39.8 MB
SQLServer2005-KB954606-x86-ENU.exe	33.1 MB

Answer 2

IA64 for Itanium Servers

x64 for 64 bits Servers

x86 for 32 bits Server

 

Rodolfo Parrado Gutíerrez

MVP Security

Bogota - Colombia

 

Answer 3

I have a client who is receiving this same "unable to load client print control" pop-up.  I have checked all 4 servers.  KB956391 was not installed, though a few other KBs were installed around Oct 1.  Automatic Update shows that KB956391 is downloaded and ready to be installed.

 

I just received this phone call and am not sure when this problem began.  Just need to get it fixed.  Everything I've found points to KB956391, but this doesn't appear to be the issue.

 

Any thoughts?

 

Thanks,

Kevin

Answer 4

Hi Kevin,

 

KB956391 typically is installed on the client machines. Once it is installed on the client machines, the killbit is active and users are not allowed to use the old Client print controls to print.

 

In order to resume printing, the report servers must also be updated with the the latest CU release or the latest GDR release, which can be installed via Microsoft Update or through the links above.

 

In a nut shell, both the Report Server and the clients need to be updated.

 

Answer 5

I've installed SQLServer2005-KB953752-x64(KB954607) service pack to our SSRS (SQL Server 2005 SP2, SSRS version 9.00.3282.00) server. It seems the RSClientPrint.cab was not updated. I've extracted the RSClientPrint.cab to a folder and checked the version of rsclientprint.dll and it is still 2005.90.3200.0. Why wasn't the RSClientPrint.cab updated by the service pack? Where can I get hold of the new cab?

 

 

Answer 6

I believe I've found the solution to my problem. For those having the same problem after installing SQLServer2005-KB953752-x64(KB954607) service pack, please check the version of your Reporting Services by accessing http://<SERVER>/ReportServer. The version should be displayed in that page and it should be 9.00.3282.00. Now extract the files from RSClientPrint.cab and check the version of the rsclientprint.dll, it should also be 2005,9,00,3282,00. If it is not, then the service pack did not update the RSClientPrint.cab file. I'm not sure if it is allowed/legal, but you can extract the new RSClientPrint.cab from the service pack file itself. I myself extracted this to fix my problem, and I can assure everybody that my Sql Server 2005 is licensed. Just wondering why the service pack did not update the specified cab file in the first place.

Answer 7

We have released an updated SharePoint add-in that addresses the client print problem for English customers.  We are providing English immediately and are working to release all localizations of the SharePoint Add-in as soon as possible.

 

Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies Download Page:

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

 

To use this version of the Reporting Services Add-in, the SQL Server Reporting Services server deployment used in conjunction with the Reporting Services Add-in must be patched with the updates listed under Microsoft SQL Server in Microsoft Security Bulletin MS08-052.

 

Thanks,

-Lukasz

 

[e-mail]

 

 

Answer 8

I'm not sure how to even sort through all of this information. All of our clients are running SQL 2005 SP2. They are also using the ActiveX control to print reports via the report viewer. On a few clients we have had to install report viewer 2005 SP1.

 

What other patches (with regards to this thread) have been released that would be considered critical?

 

Or should I completely disregard this thread since all of our clients are able to print via ActiveX just fine?

 

Answer 9

 

I've installed SP2 and the security update and I still have users that can't print reports and aren't prompted to install the active X control.

 

Answer 10

Brad Syputa - MS wrote:

In a nut shell, both the Report Server and the clients need to be updated.

 

Why do the clients need to be updated? This doesn't make any sense. If I upgraded the report server to SP 2 for SQL Server 2005 (KB921896) and installed the fix (KB954606) what else needs to be installed? I have clients who haven't been able to print for over a week.

 

Thanks!

Answer 11

Web Server is up to date
Client machine is up to date
Sql server is up to date.
Sql server 2005 is up to date.
ReportingServicesWebUserInterface.dll is version 9.0.3073.0
Microsoft.ReportingServices.Diagnostics.dll is version 9.0.3073.0

Dev box is up to date.

On control, register of viewer is <%@ Register TagPrefix="rsweb" Namespace="Microsoft.Reporting.WebForms" Assembly="ReportingServicesWebUserInterface" %>

In web.config httphandler is <add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, ReportingServicesWebUserInterface, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/>

webapp compiles without error but when I try to set parameters like
rvPrintRequestClientReport.LocalReport.ReportPath "mypath\myReport.rdlc"
app fails with "The method or operation is not implemented"

 

One fix that works (test machines) is removal of the two security updates that cause the problem.  Removal of these updates is not an option on our client machines. 

 

The other is a reg hack.  If you change the "Compatibility Flags" value to 0, the error goes away.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{FA91DF8D-53AB-455D-AB20-F2F023E498D3}]
"Compatibility Flags"=dword:0x00000000 (0)
"AlternateCLSID"="{41861299-EAB2-4DCC-986C-802AE12AC499}"

This is also really undesirable.

 

I'm really looking for working solution to rebuild webapp with new reference.

 

Answer 12

aferoce - The clients are updated when they select to print from an updated server. The updated print control will be downloaded when they select to print the first time after the server is updated. If the clients are already connected, I would recommend also restarting IIS to clear any cache.

 

savaBien - Make sure you update your webserver with the latest version of the Report Viewer control.

 

 

 

 

Answer 13

I installed the updated report viewer control and it appears to have resolved my solution.

 

The newest problem I have is if I click "Print Layout" within Preview mode the entire report shows up in Black.

 

I've been using SSRS 2005 for almost two years and this issue just started for me today. I use the Print Layout Mode all the time so I know it worked as recently as last week. I feel confidant that this black screen is related to these upgrades. Is anyone else having this issue?????

 

Any suggestions would be greatly appreciated!

 

Amedeo 

 

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

Answer 14

Hi aferoce,

 

The black background is related to an update to the OS. We do have this fixed in the full cumulative update package #9.

 

The GDR package you have installed only has the security updates and not all of the product hotfixes, which are in the CU.

 

http://support.microsoft.com/kb/953752/en-us

 

 

Answer 15

 

I installed the hotfix and the print layout screen no longer appears in black.

 

Thanks for your assistance.

Answer 16

I have run the Microsoft Report Viewer Redistributable 2008 SP1 on the web server.  In fact I ran Microsoft Report Viewer Redistributable 2008 SP1 on dev box (running localhost is where error happens when testing web app)  This did not help. 

 

Answer 17

 

我們自己經過測試，只要Install 兩個服務器和客戶端的更新，就可以解決問題！

1.SQL Server 2005 Service Pack 2 安全性更新 (KB954606)

http://www.microsoft.com/downloads/details.aspx?displaylang=zh-tw&FamilyID=4603c722-2468-4adb-b945-2ed0458b8f47

2. Windows Server 2003 的 ActiveX Killbit 安全更新程序 (KB956391)

http://www.microsoft.com/downloads/details.aspx?FamilyID=43c9f139-6432-4585-9f40-11610ce1470a&DisplayLang=zh-cn

3. Windows XP 的 ActiveX Killbit 安全更新程序 (KB956391)

http://www.microsoft.com/downloads/details.aspx?FamilyID=f6132174-3c1f-4328-9cb7-e4334ec31e64&DisplayLang=zh-cn

 

更新是否成功，請查看Active X的對比較:

 

For diagnostic purposes, here is the properties of the old and the new ActiveX objects.

	Old ActiveX	New ActiveX
FileName	RSClientPrint.cab	RSClientPrint.cab
Class Name	RSClientPrint Class	RSClientPrint 2005 Class
CLSID	{FA91DF8D-53AB-455D-AB20-F2F023E498D3}	{41861299-EAB2-4DCC-986C-802AE12AC499}
Version	2005.90.1399.0	2005,90,3073,0
Version of the rsclientprint.dll included	2005.90.1399.0	2005,90,3073,0
Version of the gdiplus.dll included	5.2.3790.1830	5.1.3102.3352

Answer 18

Hi,

 

I have a report FileName.rdl, this report has three paramters like Start date, End Dates as Calender and Customer Name as Dropdown. I have two values in Customer Name Dropdown. for Eg: Ravi, Rajesh. I have two Subscriptions for the report with Start Date, End Date for the Last One week and Customer Name for Ravi and Rajesh.

The subscriptions were working, but the report are delivered as FileName.xls.

I need to get the Reports as Rajesh (Start Ddate-End Date).xls for the one with Customer Name as Rajesh and Ravi(Start Ddate-End Date).xls for another one.

Could anyone help me in this regaard.

Answer 19

We have completed posting all localized versions of the Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies on the Download Page:

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

 

To use this version of the Reporting Services Add-in, the SQL Server Reporting Services server deployment used in conjunction with the Reporting Services Add-in must be patched with the updates listed under Microsoft SQL Server in Microsoft Security Bulletin MS08-052.

 

Thanks,

-Lukasz

Answer 20

We are at the cross roads with this question? We all know If the client is updated with the patch and the server is not updated- Reporting Services will not print on the client.

The question is what happens when the Server is updated and that the client is not updated with the patch.... it will install the newer version of activeX but will it work or do we need to have the client updated as well? We are kind of up in the air to push this update because majority of our client machines haven't updated with the patch.  

Answer 21

Hi John,

 

The client is really not a patch. It is a setting (killbit) to keep the old control from working. If the server is updated, the new patch will be installed on the client whether or not the killbit has been applied.

 

Answer 22

John - let me clarify:

 

Let me start with some definitions so we're on level terms:

client - a computer where a user will want to print a report using the ActiveX client print control

server - a computer on which an reporting services server is running or where the reporting services SharePoint Add-in is installed or the Report Viewer control is embedded in an application.

 

When you patch your SSRS server, you need to ensure all the components I list under the server tag above are also upgraded to the latest release of the component.  So if you have the Reporting Services SharePoint Add-in deployed, or you have the Report Viewer control deployed in server mode, you will need to patch these IN ADDITION to the SSRS server itself.

 

After you patch all the server components, when your clients go to print a report, they will be prompted to download a NEW ActiveX control.  That ActiveX control will allow users to print.  The clients therefore automatically get the updated ActiveX control.  As always, you should test with a representative set of low privilege client machines to ensure your user base will be able to install the new ActiveX control - sometimes users don't have enough permission to install the controls.

 

Hope that helps,

-Lukasz

 

Answer 23

Brad Syputa said:

 

 Please note: If you are using your own Web Service for your server mode Report Viewer report with Active X print, you will need to install the latest redist in the link below on the web server.

If you do not patch your server and your clients do get patched with the Killbit, then you will not be able to print. Patching the server is the recommended solution.

2. Local mode and printing. Concurrently, we released an updated Report Viewer Redist. You can find the redist here: http://www.microsoft.com/downloads/details.aspx?FamilyID=bb196d5d-76c2-4a0e-9458-267d22b6aac6&DisplayLang=en

 

I have patched both the server and the client machine with the Visual Studio 2008 Report Viewer SP1 redist from this link: http://www.microsoft.com/downloads/details.aspx?FamilyID=bb196d5d-76c2-4a0e-9458-267d22b6aac6&DisplayLang=en

It didn't work. I get the same "unable to load client print control" on the client and "Error loading resource library 0x8007007E" on the server.

We are using the report viewer with Visual Studio 2005.

Do I need to reboot the server? What else do I need to do? I am not involking the client print control in java script from my code. We do not have share point.

Is that even the right patch to be downloaded? Information overload.

---

"I have no particular talent. I am merely inquisitive." -- Albert Einstein

Answer 24

I think this has been resolved for us by installing SQL 2005 SP3.

---

"I have no particular talent. I am merely inquisitive." -- Albert Einstein

Answer 25

I am having the same issues on SQL SSRS 2008 SP1/CU1. Is there any solution for it?

Answer 26

We have installed SQL 2005 SP3 and we're still having the problem. Our version now is 9.0.4035. Only one client is working properly.
Any ideas ?

R,
GP

Answer 27

Hi,

sorry, i think it is not. I'm running SQL 2005 Version 9.0.4220 and still have the problem.
The actual rs client print version is 9.00.4035

Is there a solution planed?

Best regards
Christian