SSRS R2 Printing Error: An Error occured during printing: x80004005. This error was not happening prior to R2 being installed.

已答覆 SSRS R2 Printing Error: An Error occured during printing: x80004005. This error was not happening prior to R2 being installed.

  • Friday, July 09, 2010 7:59 PM
     
     

    Run a report and click print button, get prompted to install ActiveX control. Install that and then click on print button, get above error.

    This was working just fine prior to the R2 installation.

     

    Anyone have any insights into this?


    --ACG

All Replies

  • Monday, July 12, 2010 9:58 AM
    Moderator
     
     

    Hi,

    Based on the description, the issue might be caused because the activeX control did not update. To solve this issue, follow these below steps:

    Clear the rsclient print cache and reload it from the reporting service server:
    1. Run IE and open its Internet Options from the Tools menu.
    2. In the Internet Options window box, click "Settings" button under Browsing history in General tab.
    3. In the "Temporary Internet Files and History Settings" window box,click "View Objects" button.
    4. In the opening window, select all the dll/rll/inf files with "rsclientprint" prefix and delete them.
    5. After the above steps, close all window boxes and reopen IE to access a report, click the print icon, and reinstall the activeX control when get prompted, then try printing this report again to see if it works. If the issue persists, continues with the subsequent steps,

    Deploy the control manually:(the following files is of SSRS 2008, but the steps can apply to SSRS 2008 R2)
    1.       Go to C:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin on the report server and copy the rsclientprint.cab file
    2.       Extract the files from the rsclientprint.cab file.
    3.       Copy all the files to the client computer to Windows\Downloaded Program Files (you might need to do it using the command windows)
    c:\print\RSClientPrint.dll
    c:\print\rsclientprint.inf
    c:\print\RsClientPrint_1028.rll
    c:\print\RsClientPrint_1031.rll
    c:\print\RsClientPrint_1033.rll
    c:\print\RsClientPrint_1036.rll
    c:\print\RsClientPrint_1040.rll
    c:\print\RsClientPrint_1041.rll
    c:\print\RsClientPrint_1042.rll
    c:\print\RsClientPrint_2052.rll
    c:\print\RsClientPrint_3082.rll
    4.       Register RSClientPrint.dll by opening a command line (Start->Run) regsvr32 [path]RSClientPrint.dll

    Please let me know if you have more question,

    thanks,
    Jerry

  • Monday, July 12, 2010 8:32 PM
     
     

    Ran both sets of instructions and neither worked. Still get same error.

    The cab file I got, RSClientPrint-x86.cab (I have XP Pro 32 bit as client) had these files:

    rsclientprint_1028.rll
    rsclientprint_1031.rll
    rsclientprint_1033.rll
    rsclientprint_1036.rll
    rsclientprint_1040.rll
    rsclientprint_1041.rll
    rsclientprint_1042.rll
    rsclientprint_1046.rll <<not in your list
    rsclientprint_1049.rll
    <<not in your list
    rsclientprint_2052.rll
    rsclientprint_3082.rll


    --ACG
  • Friday, July 16, 2010 1:58 PM
     
     
    Anyone found any solution to this? We may have to roll back to R1 if there isn't a fix.

    --ACG
  • Tuesday, July 20, 2010 10:04 PM
    Moderator
     
     Answered

    Hi ACG,

    I need some more context to help you out.

    Are you using Report Manager to view the report and print?

    What is the version of the RSClientPrint.Cab and content in the rsclientprint.inf that is in the Report Server\Bin directory on the server machine?

    What is the version of report server that shows when you go to http:\\machinename\reportserver?

    What is the content, on the client machine, of the rsclientprint.inf file in your downloaded program files directory?

    On the Report Server, there is a log file generated. What is the content of the log file for the time in which you are printing? The error should populate in that log corresponding to the print time.

    (From your post to Microsoft Connect. We are looking at your bug.).You do not mention having Image rendering in your available extensions. Make sure that you have Image in your rendering extensions. Print uses EMF, which is part of Image. <Extension Name="IMAGE" Type="Microsoft.ReportingServices.Rendering.ImageRenderer.ImageRenderer,Microsoft.ReportingServices.ImageRendering"/>
       

     


    Brad Syputa, Microsoft Reporting Services This posting is provided "AS IS" with no warranties.
    • Marked As Answer by ACG Tuesday, July 20, 2010 11:21 PM
    •  
  • Tuesday, July 20, 2010 11:20 PM
     
     

    Yes, that fixed it!!

     

    Now why wouldn't that Image printing extension be part of the default extensions?

     

    And can you guys put some informative error messages in there please?


    --ACG
  • Wednesday, May 18, 2011 12:09 AM
     
     
    I'm having same issue.  Upgraded from SQL 2005 SP4 to SQL 2008 R2 and any PC that had the RSClientPrint installed gets the same error.  Try above fixes and still have issue.  All other PC's that are installing RSClientPrint for the first time have no issues.
  • Wednesday, May 18, 2011 4:19 PM
    Moderator
     
     

    Hi Beratung,

    Have you installed the latest CU of SQL 2008 R2? Not that I know it will fix your issue, but it will contain all bugs and fixes that we are aware of. Otherwise, it sounds like there is a conflict of some sort on the impacted systems between the two installs. Uninstall and reinstall is probably the best way to clean it up.


    Brad Syputa, Microsoft Reporting Services This posting is provided "AS IS" with no warranties.
  • Tuesday, May 24, 2011 1:18 PM
     
     

    Hi Brad Syputa,

        I occurred same issue. Can't print report in ReportViewer. But I use Report Manager, it can print report.

        ReportViewer is from vistul studio 2010. error message is "An error occurred during printing:0x80070057"

       My operation system is XP.

     

  • Thursday, June 30, 2011 3:04 PM
     
     Proposed

    I had this issue on my windows 2008 TS with users running SRS Reports.  To slove the issue we had to give the users write access to "c:\windows\downloaded program files"

    • Proposed As Answer by dman1234512345 Thursday, June 30, 2011 3:04 PM
    •