We have a web application that uses ReviewViewer controls. When a user with Internet Explorer 9 clicks the print button on the control, IE crashes. The fundamental problem is due to IE trying to install the rsclientprint DLL on the client's PC. This problem is reproducible. I've found quite a few other posts with this problem, but haven't found a clear solution. The environment: The server is running Windows Server 2008 R2 and SQL Server 2008 SP2 Web Edition. All patches are up to date. This server and its web application have been running for many months with no one reporting this problem until recently. Our development environment is Visual Studio Pro 2010 with ReportViewer 10, with all updates installed. We can reproduce the problem with clients running Windows 7 64-bit and IE 9 64-bit. The problem does not appear to affect PCs running Windows XP with IE 8. We are not able to test other PC configurations. This issue was first noticed a few days ago after a number of Microsoft updates were recently installed. Since most of our customers aren't running the exact client environment described above, this problem may have existed, but gone unnoticed, for a few months. Workaround: Following suggestions posted by others, if the client PC adds our web site the IE's trusted sites, the rsclientprint DLL installs okay and prints without a problem. Remaining issue: We don't control our customers' PCs, so we can't add our web site to their list of trusted sites. Each case has to be handled as a support issue one at a time, after the customer has been experiencing crashes. It makes us look like our product is defective, and we just can't have that. Is there a solution we can implement on our server or as part of the Visual Studio environment that will fix this problem? Sandy Gettings

Hi sandygettings, Thanks for your question. Based on my research and experiences, the issue is with Reporting Services SP2 and has been fixed in Cumulative Update 2 for Reporting Services 2008 Service Pack 2. There is one similar thread had handled by other partner, the more information and detail steps please refer to: http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/799e7c86-1d2d-445f-9b18-687c1474e0a7. Hope it helps you. If your issue still exists, please feel free to let me know. Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.

Thanks for the link to the other thread. I had found it before, and my impression was that it recommended installing new CAB files by hand (which we tried, but it didn't help). We'll give the Cumulative Update a shot ASAP. Sandy Gettings