I am getting the following two error messages when using the new ReportViewer v10 control after pressing the toolbar print button. I am only seeing this error inside of a modal popup window in MSIE. The print button in a normal popup window doesn't have this error. An error occurred trying to get the current window Error: Could not complete the operation due to error 8007f305. If anyone knows of a quick fix, please let me know. Thank you. VS2010, MSIE 8, SQL Server 2008.

Another symptom is that whenever I press the print button I am prompted to install the ActiveX control, even if it is already installed. Perhaps this is somehow related to extra security settings in modal windows that interferes with ActiveX controls. This is the line in the rendered HTML that throws the error: printObj.Print(printInfo.PrintRequestPath, printInfo.PrintRequestQuery, printInfo.ReportDisplayName);

I created very basic report and a very basic Web page to test this specific error, and I get the error 100% of the time. I tried setting the MSIE security down to low, but it didn't help with the issue. In my searching I saw references and Microsoft Connect entries to this error for SQL Server 2005, which was supposedly fixed with a service pack. It looks like the bug has resurfaced with the latest version of the Web controls. Some possible workarounds I can think of: -Revert the entire site back to the v9 version of the controls. -Remove all modal windows in the Web site. -Remove the print button and use the normal Web browser print function.

Hi usp, I can reproduce the issue. In Report Viewer control, we write a new page with the RSClientPrint ActiveX control to the client while clicking the print button. Generally speaking, we use the Response.Write to write to a HTML page to the client. The HTML page has a mark like this: <OBJECT ID="RSClientPrint" CLASSID="CLSID:RSClientPrint ID here" CODEBASE="<URL to the .CAB file>#Version=<your application version information>" VIEWASTEXT></OBJECT> So, the issue seems to be caused by that the modal dialog does not allow us to open a new page with ActiveX. This should be a security issue. I am still investigating it. If there is any update, I will inform you. Currently, I would suggest you using normal window instead to fix the issue. If there is anything unclear, please feel free to ask. Thanks, Jin ChenJin Chen - MSFT

Hi, I have the same problem... Is there any news about this. A change from modal dialog to normal window willl break code that was previously running. Thank you for your time, Luis Neves

The only news is that you cannot run the v10 version of the ReportViewer control until the bug is fixed. I reverted back to the v9 version of the control.

Any update yet? It has been quite some time, I hope microsoft has a solution to this issue, as I am also experiencing it. And I am experiencing it in an application we have procured from a vendor. In other words I'm unable to edit the application to use a "normal" window as Jin suggested.

Hello, We found we have the same issue. QUICK FIX; push 'ctrl'+'p' Good luck!