none
Error loading resource library. (0x8007007E) when printing - after hotfix

    Question

  • Hi,

     

    I added the kB954607 GDI security hotfix to our development cluster the other day and now we're having printing problems (again...sigh). 

     

    Error loading resource library. (0x8007007E)

     

    I've tried deregistering the RSClientPrint.dll and then printing to have it install again, but that didn't work for me. 

    Wednesday, October 22, 2008 3:06 PM

Answers

All replies

  • I've found some info on this issue.

    Says to run

     

    C:\WINNT\Downloaded Program Files>regsvr32 rsclientprint.dll

     or

     

    C:\WINNT\Downloaded Program Files>regsvr32 rsclientprint.dll /u

    to unregister and then reregister.

     

    This didn't fix my development test.  Unregistering gave the same error on production.  Could this control be stored in different places for different versions of reporting services?  I have several versions of RS with different print controls - could things be getting corrupted/confused?

     

     

     

    Wednesday, October 22, 2008 11:36 PM
  • Can you checked the date for RSClientPrint.dll? If it is 2007-2-10, that means this file is old one, but in IE Add-On management the class name is RSClientPrint 2005 Class, that is not inconsistent. I've found this problem on some PC of my user, after I update the correct dll files, the problem solved.

    Thursday, October 23, 2008 7:27 AM
  • Hi Sam,

     

    Try the following steps to update the dll for IE.

    1. Unregister RSClientPrint.dll
    2. Open Internet Explorer
    3. Got to Tool - > Internet Options
    4. Click on ‘Programs’ tab
    5. Click on ‘Manage add-ons’
    6. Select and Delete the ‘RSClientPrint Class’ ActiveX Control
    7. Select ‘Security’ tab
    8. Select ‘Intranet Zone’ and click on ‘Custom Level’
    9. Enable ‘Automatic prompting for ActiveX controls’
    10. Select ‘Prompt’ for ‘Download signed ActiveXcontrols’ and ‘Run ActiveX controls and plug-ins’
    11. Restart the Internet Explorer
    12. Try to print the report, this time it will prompt you to run the ActiveX  controls and plug-ins
    13. Click 'Yes'


    If there are any more questions, please let me know.
    Thanks.

    Tuesday, October 28, 2008 6:40 AM
    Moderator
  •  

    Hi,

      Thanks for the information. I am trying to follow the steps but i coudn't fnd any options for delete the activex control. Why is it this activex control often getting sme problem and we need do this quiet often.

       is there any latest version

     

    Thanks & Regards

    Rajesh V

    Tuesday, October 28, 2008 11:51 AM
  • The following worked like a charm for me:

    Go to C:\WINDOWS\Downloaded Program Files, right click on RSClientPrint Class and select remove. 

    Tuesday, October 28, 2008 2:13 PM
  •  

    Xiao-Min

     

    Thanks for your help.

     

    I have followed your directions and am now prompted to install the SQL/Microsoft ActiveX control, but I still get the same error after it installs.  Any other suggestions?

     

    Sam

     

     

    Wednesday, October 29, 2008 5:07 PM
  • I'm getting the same error.  I can get to the point that I'm prompted to install the active x control, but it fails saying "Error loading resource library"

     

    Anyone??? Bueller??? Bueller???

     

    Thanks,

    Chris

    Tuesday, November 4, 2008 10:35 PM
  • We do not get the error in our QA environment that has SP1 installed.  However, we have had some issues with SP1 on production and have not installed it on production.

    Tuesday, November 4, 2008 10:50 PM
  • found some other directions:

     

    Try this:
    * Close MS Internet Explorer
    * Erase all content of C:\WINDOWS\Downloaded Program Files\ directory
    * Open MSIE and navigate to report you want to print
    * Click the Print button - you'll be asked to install ActiveX printing component.
    * Confirm the installation
    * Confirm the error message
    * Copy all RSClientPrint*.rll files from C:\Windows\ to C:\WINDOWS\Downloaded Program Files* Try to print the report again - Voila, it works now :-)

     

    Seems a little drastic - deleting everything.

     

    It fixed my problem on my production server - 9.0.3257 version

    not on dev - 9.0.3282 .

     

    I'm sick of this darn print control.

    Tuesday, November 4, 2008 11:45 PM
  • I also tried just copying the *.rdl files in the command prompt without deleting everything, but it didn't work until I removed everything and then copied again.

     

    Tuesday, November 4, 2008 11:49 PM
  •  

    This sounds good in theory.  However, I can't paste anything into my c:\windows\downloaded program files* directory.  Any ideas?

     

    Thanks,

    Chris

    Thursday, November 6, 2008 5:36 PM
  •  

    Go to the command line and use the xcopy command.

     

    xcopy /?

     

    for help.

    Thursday, November 6, 2008 5:47 PM
  • My solution was to do this:

     

    Install 3282 patch on server (already had this)

     

    Install Report Server redist (http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=4038983&SiteID=1) - on client and server.  Not sure if both are necessary.

     

    Go to the c:\windows\downloaded program file

     

    'Remove' the Report Server Client print controls. 

     

    Restart the browser and print. 

     

    The only diff from what I've been doing would be the install of the redist.

    Thursday, November 6, 2008 7:16 PM
  • This has only worked for one computer out of 6 - if anyone has any other suggestions I'd appreciate them.

    Monday, November 10, 2008 5:40 PM
  •  

    This is what i did to fix the above the error message.. I got the above error message after i went installed this on my computer

    http://www.microsoft.com/downloads/details.aspx?familyid=82833F27-081D-4B72-83EF-2836360A904D&displaylang=en

    after u install this make sure and u restart IIS (IISReset). and then go run that report..

     

    The first time you run the report u would get a error message that says "Unable to Load Client print" click on and then on u will get a bar on top of the IE to install the Active X control Go ahead and install it.. and then it will try to refresh that page and then hit retry.. click on the print control and it prompt to install the active x control and then install it.. and then u will see the print window pop on your machine..

     

    I have tried doing it in my test server which is Windows Server 2003 and has sql server 2005 and SSRS 2005 on the same computer.

     

    Hope this helps.

     

    Thanks,

    Karen

    Monday, November 10, 2008 6:18 PM
  • I'm a bit confused all the MSFT stuff on this fix says to install the 2008 Report Viewer distributable. 

     

    I uninstalled the 2008, installed the 2005 and restarted iis and cleared the .dll/class from the client machine.  Still no luck.

    Monday, November 10, 2008 6:46 PM
  • I am using 2005 and not 2008

    I have tried this solution on two or 3 computers and it works fine..

    Monday, November 10, 2008 6:51 PM
  • I followed the post at http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=4038983&SiteID=1 

     

    It's just not working out.  I got it to work on my desktop, but it just started working randomly and I can't reproduce on a test workstations. 

    Monday, November 10, 2008 8:57 PM
  • Do u have the same version of the report viewer as of in the link that i provided..

     

    Monday, November 10, 2008 10:02 PM
  • Yes, I tried installing that on the server then removing and unregistering the RSClientPrint.dll - same outcome.  BUT, the 2008 report control works for my pc - just not for anyone else.  I think the 2005 and 2008 refer to Visual Studio versions. 

     

    Are you installing this on your client machines as well?  I did try that, but that's not how I've been informed that we need to distribute to most users, since we don't do local mode printing.

    Monday, November 10, 2008 10:35 PM
  •  

    No i just installed it in the report server
    Monday, November 10, 2008 10:38 PM
  • I have deregistered the dll

    removed the active x addon

     

    tried the report again, it asks me to install the file which is fine.

    still getting error loading resource library

     

    waiting to hear back from Microsoft

    Monday, November 17, 2008 2:38 AM
  • I got the same error on one of our production machines today and this is what i did..

     

    First i had installed this link  http://www.microsoft.com/downloads/details.aspx?familyid=82833F27-081D-4B72-83EF-2836360A904D&displaylang=en on my webserver and  then gave IIS reset.

     

    And then in the Client machine.. If they have already using the old report viewer control.. then go to

    C:\Windows\DownloadedProgramfiles and look for RsClient.dll and the right click on it and hit remove...

     

    Be sure your application or the internet explorer page that is using report viewer is closed.

     

    Then open IE. run that report and then hit print the button.. It will say Cannot load print Control and then click on Ok and the top double click on the active X control so that u can download...

     

    Hit retry when it asks to refresh that page.. Once that is done click on the print button again and now it should ask u install the print control and after it installs it. it will work...

     

    Thanks,

     

    Karen

     

    Thursday, November 20, 2008 9:41 PM
  • Hi Braddo,

     

    Can you provide some details about your environment?

     

    What version of RS are you using?

    What version of the Report Control are you using?

    What is in your \windows\downloaded program files\ directory?

    Do you have all of the latest Microsoft updates installed?

    Are you using the Report Control and if so, is it in Local Mode or Server mode report viewing?

     

    Brian's blog might help you: http://blogs.msdn.com/brianhartman/default.aspx

     

    Any other details you can provide would really help us nail down what your issue might be.

     

     

    Thursday, November 20, 2008 11:04 PM
    Moderator
  •  

    All,

     

    I followed the different solutions for resolving this error. I basically ran any update I could find.

    I've updated sql, reportviewer, GDI+ etc.

    Currently running on this dev. env

    Windows XP (fully patched)

    VS2005 and 2008 (both updated with the latest patches incl. those mentioned for the reportviewer control/GDI+)

    SQL Server 9.0.4028

    RS : 9.0.4028

     

    RSClientPrint.cab 

    • rsclientprint.dll  2005.090.4028.00
    • gdiplus.dll 5.1.3102.3352 (xpsp_sp2_qfe.080415-1302)

                

    It still fails with the error as stated in this threat.

    When debugging it seems to fail on the actual print method of the rsclientprint class as called in the reportviewerwebcontrol.

    **************************

    <HTML>

    <BODY onload="Print()">

    <OBJECT ID="RSClientPrint" CLASSID="CLSID:41861299-EAB2-4DCC-986C-802AE12AC499" CODEBASE="/Reports/Reserved.ReportViewerWebControl.axd?ReportSession=r0ps5ryunbbrw4mqbg1ouz45&amp;ControlID=32b7874aa88840c3a728a98959792aa5&amp;Culture=6153&amp;UICulture=9&amp;ReportStack=1&amp;OpType=PrintCab#Version=2005,090,4028,00" VIEWASTEXT></OBJECT>

     

    (.......removed)

     

    RSClientPrint.Print("\/Reports\/Reserved.ReportViewerWebControl.axd", "ReportSession=r0ps5ryunbbrw4mqbg1ouz45&ControlID=32b7874aa88840c3a728a98959792aa5&Culture=6153&UICulture=9&ReportStack=1&OpType=PrintRequest", "xxx")

     

    }

    </script>

    </BODY>

    </HTML>

    ****************************************

     

    Thanks for any info you can provide me. I suspect the CLSID is part of the issue but no clue how to resolve this.

     

    Kind regards,

    Bram

     

    Thursday, December 4, 2008 2:47 PM
  • I too have followed all instructions and am not succeeding on this issue.  Brad tried to help, but recommended we contact PSS.  Unfortunately this is not an option for me right now.  I've managed to get it working on one client machine, but cannot replicate that success on test machines. 
    Thursday, December 4, 2008 4:49 PM
  • Hey Bram,

     

    What is in your \windows\downloaded program files\ directory? The resource load error is most likely for one of the rsclientprint.rll files.

     

    We have seen several customers encounter this issue, but so far we have not been able to isolate the cause, which is most frustrating to them and for us.

     

     

     

    Thursday, December 4, 2008 5:59 PM
    Moderator
  • I'll chime in here...same versions.

    Both are XP Pro SP2

    On a non-working machine:

    RSClientPrint 2005 Class
    ID: {41861299-EAB2-4DCC-986C-802AE12AC499}
    version:2005,90,3282,0

    On a working machine:

    RSClientPrint 2005 Class
    ID: {41861299-EAB2-4DCC-986C-802AE12AC499}
    version:2005,90,3282,0
    Thursday, December 4, 2008 8:04 PM
  • Hey Sam,

     

    Kind of an oxymoron where it works and it does not work.

     

    Where are all of the files from the rsclientprint.cab file located on each client machine?

     

    Friday, December 5, 2008 12:51 AM
    Moderator
  • Hi Brad,

     

    Thanks for you prompt reply and sorry for the delay on my end.

     

    I have the following files in my dl prog. dir:

    2x Java runtime env.  1.6 etc.

    RSClientPrint 2005 class Version 2005,90,4028,0

     

    That's it currently.

     

    One of the articles talked about removing most items here.

    I did so but can't do without my java runtime. (some business related appl. rely on it.)

     

    I did try to copy all .rll files there as well but this seems sligthly odd to me. (as far as I know those were usually located in system32?)

     

    Thanks again,

    Bram

     

     

     

     

    Friday, December 5, 2008 7:14 AM
  •  

    If they are the files we are talking about then - C:\WINNT\Downloaded Program Files.
    Friday, December 5, 2008 4:14 PM
  • I'm having the same issue.  I used to get the Unable to load print control error, now I get this error.

    I've tried every solution I can find on these forums with no luck.

    Most of the issues I've read about seem to be Sharepoint specific, although I'm getting this error from MS CRM.
    Friday, December 5, 2008 6:36 PM
  • Can several of you please run from a command prompt and post the results?

     

    dir /s "%windir%\downloaded program files\*clientprint*"

     

    Possible solution would be to go into Internet Explorer and Manage Add-ons. Remove all RS client print related active X controls.

     

    Friday, December 5, 2008 7:36 PM
    Moderator
  • On the working machine:

    08/05/2008  09:08 AM           582,168 RSClientPrint.dll
    08/05/2008  09:09 AM             1,600 RSClientPrint.inf
    10/14/2005  03:44 AM            10,968 RSClientPrint_1028.rll
    10/14/2005  03:44 AM            11,480 RSClientPrint_1031.rll
    10/14/2005  03:44 AM            10,968 RSClientPrint_1033.rll
    10/14/2005  03:46 AM            11,992 RSClientPrint_1036.rll
    10/14/2005  03:47 AM            11,480 RSClientPrint_1040.rll
    10/14/2005  03:47 AM            10,968 RSClientPrint_1041.rll
    10/14/2005  03:47 AM            10,968 RSClientPrint_1042.rll
    10/14/2005  03:47 AM            10,968 RSClientPrint_1043.rll
    10/14/2005  03:49 AM            10,968 RSClientPrint_1046.rll
    06/28/2006  04:26 PM            11,552 RSClientPrint_1049.rll
    10/14/2005  03:49 AM            10,968 RSClientPrint_1053.rll
    10/14/2005  03:49 AM            10,968 RSClientPrint_2052.rll
    10/14/2005  03:49 AM            11,480 RSClientPrint_3082.rll

    On the non-working:

    08/05/2008  09:08 AM           582,168 RSClientPrint.dll
    08/05/2008  09:09 AM             1,600 RSClientPrint.inf
    06/28/2006  04:26 PM            11,552 RSClientPrint_1049.rll
    Friday, December 5, 2008 7:44 PM


  • 08/05/2008  05:58 PM           576,528 RSClientPrint.dll
    08/05/2008  05:59 PM             1,600 RSClientPrint.inf
    10/14/2005  01:46 AM            11,992 RSClientPrint_1036.rll
    10/14/2005  01:47 AM            11,480 RSClientPrint_1040.rll
    10/14/2005  01:47 AM            10,968 RSClientPrint_1041.rll
    10/14/2005  01:47 AM            10,968 RSClientPrint_1042.rll
    10/14/2005  01:47 AM            10,968 RSClientPrint_1043.rll
    10/14/2005  01:49 AM            10,968 RSClientPrint_1046.rll
    06/28/2006  02:26 PM            11,552 RSClientPrint_1049.rll
    10/14/2005  01:49 AM            10,968 RSClientPrint_1053.rll
    10/14/2005  01:49 AM            10,968 RSClientPrint_2052.rll
    10/14/2005  01:49 AM            11,480 RSClientPrint_3082.rll
    Friday, December 5, 2008 8:19 PM
  • Sam - You are missing a lot of RLL files in the non-working scenario. How was the control installed? English US is RLL with 1033 in the name. 1049 is Russian.

     

    Kevin - For some reason, you do not have all of the RLL files either. How did the control get installed as well?

     

    If you are using Reporting Services Server, you can find an RSClientPrint.cab file in the program files directory. In that cab is all of the RLL files. Please check to make sure the cab is correct.

     

    Rather odd that rll files are missing in both cases. The biggest question again is how did the control get installed originally and where did the files come from.

     

    If anyone would like to take off line for more direct contact, email me at bradsy@removemicrosoft.com. If we can get an answer together, we can post back here to help others.

     

     

     

    Friday, December 5, 2008 10:58 PM
    Moderator
  • For me I get:

     

    On working machine:

     

    08/05/2008  05:58 PM           576,528 RSClientPrint.dll
    08/05/2008  05:59 PM             1,600 RSClientPrint.inf
    10/14/2005  03:44 AM            10,968 RSClientPrint_1028.rll
    10/14/2005  03:44 AM            11,480 RSClientPrint_1031.rll
    10/14/2005  03:44 AM            10,968 RSClientPrint_1033.rll
    10/14/2005  03:46 AM            11,992 RSClientPrint_1036.rll
    10/14/2005  03:47 AM            11,480 RSClientPrint_1040.rll
    10/14/2005  03:47 AM            10,968 RSClientPrint_1041.rll
    10/14/2005  03:47 AM            10,968 RSClientPrint_1042.rll
    10/14/2005  03:47 AM            10,968 RSClientPrint_1043.rll
    10/14/2005  03:49 AM            10,968 RSClientPrint_1046.rll
    06/28/2006  04:26 PM            11,552 RSClientPrint_1049.rll
    10/14/2005  03:49 AM            10,968 RSClientPrint_1053.rll
    10/14/2005  03:49 AM            10,968 RSClientPrint_2052.rll
    10/14/2005  03:49 AM            11,480 RSClientPrint_3082.rll
                  15 File(s)        723,856 bytes

     

     On Non Working:

     

    08/05/2008  05:58 PM           576,528 RSClientPrint.dll
    08/05/2008  05:59 PM             1,600 RSClientPrint.inf
                   2 File(s)        578,128 bytes

     

    Wednesday, December 10, 2008 8:47 PM
  • I haven't heard from brad for a day or two, so I'll post what worked for me.

    As Brad said, I did not have the 1033.rll file.  I copied this from another working computer to a non-working machine and the problem was fixed.  The XCopy DOS command must be used - you cannot cutnpaste/dragndrop.  For some machines I found directories labeled CONFLICT.1 or CONFLICT.2.  It was necessary to delete them with the CMD prompt using DEL and RMDIR.

    You can see if you have these directories by running the listing command Brad posted above.

    We distribute this activeX to our clients with electronic software distribution, so we will update the .cab which that is using and that should fix all of our standard users.

    I'd still like to resolve the issue with only the 1049.rll file being delivered. 

    The .cab on our server contains all the files - 13 .rlls I believe.


    Wednesday, December 10, 2008 9:33 PM
  • Aside from copying the cab files from a working machine, where else can I get the files?  I'm pretty sure I must have old files from before the hotfixes or before we upgraded to CRM 4.0 during which time we also upgraded to SQL 64bit edition.  There have been a lot of changes to our environment, so it might be hard to pinpoint what went wrong when.
    Thursday, December 11, 2008 3:41 PM
  • I finally got it working!!!
    Here is what worked for me:



    Downloaded RSClientPrint.cab (Can't remember where i got it from.  Sorry)

    Extracted the cab into a folder.

    In a command prompt, navigated to the Downloaded Program Files directory.

    Ran xcopy c:\FolderName /e    (which copies all the files to the current directory)

    Restarted IE, and it worked.

    I hope this helps anyone still having this problem.
    Thursday, December 11, 2008 4:27 PM
  • Can someone please help me out.  I still have the same issue about error loading resource library.
    I have tried everything?

    We are running reporting services 2000 and the client printing is not working!
    What do i need to do on the client?  What do I need to do on the server ?
    Monday, January 5, 2009 7:57 PM
  • If you are missing some of the .rll files from the Downloaded Program Files folder, try looking in your System32 folder. On several machines I found an old copy of RSClientPrint.dll and 12 of the .rll files (all but the 1049/russian file). 

    Once I found the files in System32, I did the following:
    • Unregistered the RSClientPrint.dll from System32
    • Deleted all of the RSClientPrint* files from System32
    • Removed (Right-click > Remove) the currently registered RSClientPrint control the Downloaded Program Files directory
    • Assuming that you have applied CU9 (or later) or SQL Server SP3, the when you open the report and click the print button, the new control is downloaded and installed in IE.

    One thing that I did realize after the fact from a brief mention by Brad in one of the threads is that the SQL Server Redistributable 2005 SP1 or 2008 is NOT required on the server at all.

    Hope that helps.

    Matt

    Monday, January 5, 2009 11:50 PM
  • I was really looking for what steps I need to take on the server and client.  Do I need to patch the server with the KB update ?  Should I install all updates on the server?
    Tuesday, January 6, 2009 2:02 PM
  • Yes, you should patch the SSRS server with all the security updates.   When you do that, the new client print control should automatically download and install on the client side the next time the user tries to print.

    Hope that helps,
    -Lukasz
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, January 7, 2009 7:06 PM
    Moderator
  • I'm still having issues with this.

    I'm able to get workstations functioning by placing the dlls and rlls into winnt, but we're having issues with asp.net applications that embed the reportviewer.  They are getting the unable to load library error.  I've installed the redistributable sp1. 

    Also, I've removed our manual fix from my computer and am still getting the error loading resource library error message and get no .rll files installed.  If I were to copy them to this directory, all would be well.

    Directory of C:\WINNT\Downloaded Program Files

    07/25/2002  06:13 PM            24,576 dwusplay.dll
    07/25/2002  06:13 PM           196,608 dwusplay.exe
    07/27/2004  04:48 PM           323,584 isusweb.dll
    08/19/2004  12:10 AM            24,576 MyApps.dll
    08/05/2008  09:08 AM           582,168 RSClientPrint.dll
    08/05/2008  09:09 AM             1,600 RSClientPrint.inf
    10/16/2008  02:16 PM               293 wuweb.inf

     

     

    Friday, January 30, 2009 6:42 PM
  • I just tried installing the activex for the browser on the report server.  Everything worked fine. 

    I'm thinking it's a firewall issue now.  Does anyone know how the .rll files would be blocked, but not the .inf and .dll?

    Friday, January 30, 2009 6:49 PM
  • I tried printing from the passive node of the cluster.  Reports is only running on node 1.  So it seems the .rll files make it from one computer to another.  We have a web port and SSL port open.  I can't find any documentation claiming we need anything else.
    Friday, January 30, 2009 8:57 PM
  • Did you install the updated ReportViewer distribution that contained the security fix? Brian Hartman has a great blog post available which has links to all the downloads for this GDR.

    http://blogs.msdn.com/brianhartman/archive/2008/11/05/client-print-fails-to-load-after-microsoft-update-956391.aspx

    Let me know if that doesn't solve the problem.

    -Lukasz


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, February 2, 2009 6:14 PM
    Moderator
  • Yes, did that.

    I'm thinking it's some kind of strange security anomoly in our environment.

    I had a security person try it and it worked for them.
    Thursday, February 5, 2009 5:32 PM
  • Do you have a support agreement with MS?  If so, I'd recommend calling Customer Support since it seems like on the forums we won't be able to get enough information to determine what is happening. 

    Hope that helps,
    -Lukasz
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, February 6, 2009 2:39 AM
    Moderator
  • Yes, we do, but only a certain number of hours per year - and we're working on implementing exchange this year.  Getting them is tough.

    Like I said, I had a security person remove all of her existing RSClient files and had her try the install.  That worked, all .rlls are there

    Then I tried it again on my computer. No go

    Then we had her come to my computer.  No go.

    Then we went to a training computer and both tried it.  Worked fine. 

    What could be the problem there?

    Also, where are the .dlls and .rlls being pulled from when someone is using the reporting control in c# .net app? 

    If we've installed all the proper files on their computer and regular report printing works fine, is it looking in a different location for these files?

    Thanks so much for any help you can provide. 

    edit: just went by the guy's desk who is having this problem and it's a different error....the unable to load print control one.  I think he needs to update visual studio to use the new reportviewer control - we'll see what happens.

    Sam
    Friday, February 6, 2009 9:02 PM
  • Actually did some digging and found the following at the bottom of the Security Bulletin release... so you don't have to worry about burning your support incidents.  

    http://www.microsoft.com/technet/security/bulletin/ms08-052.mspx


    For information about Security updates visit the Microsoft Virus Solution and Security Center for resources and tools to keep your PC safe and healthy. If you are having issues with installing the update itself, visit Support for Microsoft Update for resources and tools to keep your PC updated with the latest updates. 



    Friday, February 6, 2009 11:35 PM
    Moderator
  • I've tried numerous sugggested solutions for this problem, but the thing that did the trick was copying (in a command shell !!!) the .rll files to the folder "\windows\downloaded program files".
    You cannot drag and drop these in explorer, you have to go through a cmd-prompt.
    The files are in the RSClientPrint.cab, which you can find in the bin-folder of ReportingServices ( usually \Program Files\Microsoft SQL Server\MSSQL.??\Reporting Services\ReportServer\bin)

    Hope this works for you.

    Peter

    Wednesday, February 11, 2009 7:22 PM
  • Finally fixed!

    I did everything suggested on this forum, and still a persistent problem on only some of the machines. The ultimate fix was to delete all of the RSClientPrint*.* files (13 rll files, 1 inf and 1 dll) from the Windows\System32 folder. I don't think they're supposed to be there, and don't know how they got there, because they weren't on any of the machines with no printing problems. In any event, it fixed the problem on 23 computers with printing issues.

    Wednesday, March 25, 2009 4:24 PM
  • Thank you RabbitGuy! I tried everything I have ever read before and nothing ever worked... until I read your post... Thanks!
    Friday, July 3, 2009 10:17 PM
  • Man, this was a hard thing to solve! the user had 2 different versions of RSClient(which I didn't realize until I saw RSCLient somewhere and RSClient2005 somewhere else!) what helped me to solve my issue is some combination of what you all said here and it helped me to determine what should had been done in my specifical case:

    1 On Internet Explorer go to Manage Add ons> Enable\disable add ons
     Choose: Add-ons that have been used by IE
     Scroll down and find RSClientPrintClass, select it and delete it(there's a button  down at the right side)

    1 Close MS Internet Explorer
    2 Delete RSClientPrint Class (or RSClient Print Class 2005) in C:\WINDOWS\Downloaded Program Files\
    3 Delete all these files:
      RSClientPrint*.rll
      RSClientPrint.inf
      rsclientprint.dll
      gdiplus.dll (if it is there)
      Delete these files from the following directory/ies:
      C:\Windows\
      C:\WINDOWS\System32
    4.Go to regedit (start>run>regedit or regedt32 as you prefer)
      Look for the value rsclient and delete every entry and content folder
      (all these entries have to be deleted so the version coming from your SSRS Server could be the only one version in the computer) be careful and notice that you should be deleting entries corresponding to Reporting Services Client only. ONLY!

     5. Look again in regedit, look again for RSCLient, there should not be any entry for RSClient or RSClient 2005.
     6. Open Internet Explorer, go to SSRS, open the required report, click on the print button
    This will automatically update the RSSClient and finally it won't show that horrible error message saying that it's not possible to upload the library!! it was the worse headache ever!!!!

    Friday, August 21, 2009 8:50 PM
  • We are having to do this (delete all RSClientPrint*.* from system32) across our domain after the patches released in October 2009.
    Monday, October 19, 2009 9:20 PM
  • It usually happens when you change the report remote address. For example, you are on a development environment and then you need to change to a production environment, so the first

    "C:\WINNT\Downloaded Program Files\RSClientPrint" class was created pointing to the oldest report adress, as you can see clicking with mouse right button on the RSClientPrint file and then clicking on properties. That's the reason why you need to delete the actual RSClientPrint class from your windows folder, if you aren't the administrator of your machine I recommend that you tell to the administrator to create a .bat to clear this files for all the users machines through the domain machine.

     

     

     

    Monday, October 17, 2011 4:42 PM
  • That´s the solution for Client's Printing Issue using SSRS 2008 R2:

    Locate the RSClientPrint-x86.cab or RSClientPrint-x64.cab (both packages could be found into installation folder of your Reporting Services Server, like %ProgramFiles%\Microsoft SQL Server\MSRS10_50.xxxxxxxxxxxx\Reporting Services\ReportServer\bin) copy them for client's computer and unpack the correct package (depends of client's architecture) into %Windir%\System32 folder.

    Then open command prompt (elevated mode) and register the DLL using the following command:

    regsvr32.exe /s %windir%\system32\rsclientprint.dll 

    So, go to the report and then click print. If you are prompted about any installation, click yes.

    Thursday, January 12, 2012 4:27 PM
  • So glad someone had the answer! It solved my problem today! Thank you!

    ultimate fix was to delete all of the RSClientPrint*.* files (13 rll files, 1 inf and 1 dll) from the Windows\System32 folder

    • Proposed as answer by Hamiltonboy78 Wednesday, January 22, 2014 3:34 PM
    Wednesday, April 4, 2012 7:28 PM
  • That fix worked for me.

    I deleted all of the RSClientPrint*.* files (13 rll files, 1 inf and 1 dll) from the Windows\System32 folder and the RSPrintControl from C:\Windows\Downloaded Program Files and then tried to print again and the installation went through successfully.

    Wednesday, January 22, 2014 3:36 PM
  • Thanks, your suggestion solved it for me.

    Martin Bring, Sogeti Sweden Celebrating 12 years with BizTalk

    Monday, December 1, 2014 3:15 PM
  • I had to do this once again, and this time the files where not in C:\Windows\System32

    C:\Windows\SysWOW64.


    Martin Bring, Sogeti Sweden Celebrating 12 years with BizTalk

    Friday, November 20, 2015 9:58 AM