Report Viewer Print Control Crashes MSIE 9
I installed MSIE 9 to do QA testing against my Web application and MSIE 9 crashes every time I press the print button on any of the reports. Has anyone else experienced this problem, or is it working for you?
Crash Details:
Problem Event Name: APPCRASH
Application Name: iexplore.exe
Application Version: 9.0.8112.16421
Fault Module Name: rsclientprint.dll
Fault Module Version: 2007.100.1600.22
Running SQL Server 2008 (not R2), ReportViewer v9, NET 3.5sp1, MSIE 9.0.8112.16421, Win7sp1 x64.
March 15th, 2011 5:47pm
Did you use the .rdlc local report? Or .rdl report on remote report server?
Free Windows Admin Tool Kit Click here and download it now
March 20th, 2011 11:15pm
This is using a remote report server.
This is also the first time I tested the site on a computer running Win7sp1 x64, so that might be a factor as well.
March 23rd, 2011 12:07pm
Try to update SQL Server, Visual Studio and Windows to the latest version. I have rebuilt your environment, and encountered some issue, after I install all updates it works fine. :)
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2011 5:50am
I am running the latest version of Windows 7 sp1 x64 Home Premium, SQL Server 2008 Standard SP2, and Visual Studio 2010 sp1. SQL Server 2008 SP2 CU #3 came out this morning. I have not looked at the three cumulative updates for possible solutions yet.
I doubt that VS 2010 has any impact on this since this is a Web site project, so the Web site code is being compiled on the server, completely outside of Visual Studio. The report viewer redistributable control was a separate download that is installed on the
server.
I would guess that the problem is related to the report viewer v9 control not being compatible with MSIE 9 or Windows 7 x64. I only have the one Windows 7 computer running MSIE 9, so it is hard to test those variables independently. I neglected to test MSIE
8 on Win 7 before upgrading to MSIE 9, and it is hard to go back.
Perhaps the issue is something else entirely and that it is unique to my environment. I tested again right now and the error still exists and is 100% reproducible.
When you say you saw "issues," was the issue that the browser crashed, or was it just not working properly for other reasons. The error that I see is "Internet Explorer has stopped working" when I press the print button, with options for "Check online..."
and "Close the program."
I will do some more testing and searching myself. Nearly all the users accessing the intranet reporting site run Windows XP, so this issue isn't urgent for me yet.
March 25th, 2011 1:30am
I set up a test environment using SQL Server 2008 R2 Developer and I still get the same error using a basic test report. The details reflect a different version number for rsclientprint.dll:
Problem signature:
Problem Event Name: APPCRASH
Application Name: iexplore.exe
Application Version: 9.0.8112.16421
Fault Module Name: rsclientprint.dll
Fault Module Version: 2009.100.1600.1
Exception Code: c0000005
Exception Offset: 00017e7a
OS Version: 6.1.7601.2.1.0.768.3
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2011 1:02pm
If I add the domain to Trusted Sites, MSIE does not crash when the print button is pressed. I don't really see this as a solution since as a Web programmer I can't ensure that every Web site user does this. Perhaps this gives some insight into the problem
that would reveal an alternate solution.
March 29th, 2011 3:10pm
I just tried switching the the Report Viewer control v10 against SQL Server 2008 R2 and Internet Explorer 9 crashes with a different error message when printing:
"A problem with this webpage caused Internet Explorer to close and reopen the tab"
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2011 3:33pm
I confirmed that the cumulative updates that were recently released for 2008 SP2 and 2008 R2 SP0 seem to fix this issue by installing an updated ActiveX control.
I installed 2008 R2 SP0 CU7 and 2008 SP2 CU3.
This CU fix was mentioned in the Microsoft Connect bug report for this issue.
May 1st, 2011 9:39am