SQL Server Developer Center > SQL Server Forums > SQL Server Reporting Services > Unable to load client print control...The request failed with HTTP status 401: Unauthorized.
Ask a questionAsk a question
 

AnswerUnable to load client print control...The request failed with HTTP status 401: Unauthorized.

Answers

  • Tuesday, November 10, 2009 5:48 AMJin ChenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi Paulino,

     

    From your last reply, I suppose the issue is caused by the RSClientPrint control is not the newest one.

     

    So, please follow these steps to solve the issue:

    1.       Open the Report Server folder.

    By default, the folder is: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer

    2.       Open the sub folder bin.

    3.       Extract the package RSClientPrint.cab

    4.       In the extracted folder, right-click on the rsclientprint.dll, and then click “Properties”

    5.       Make sure the version is “2005.90.4266.0” from the “Version” tab. If the version is less than “2005.90.4266.0”, that means we did not apply Cumulative update package 6 for SQL Server 2005 SP3 successful. Please re-apply it.

    6.       After making sure the RSClientPrint.cab has the newest version.

    7.       Please go the client, open the Report Manager: http://<reportserver name>/reports. Please open the Report Manager, not the custom web application.

    8.       Open any report.

    9.       Click “Print” button.  If the report is printed correctly, it means the RSClientPrint control has been installed correctly on the client.

    10.   In this case, go to “C:\Windows\Downloaded Program Files”, we will see RSClientPrint.dll with version ““2005.90.4266.0”, and CLSID “{0D221D00-A6ED-477C-8A91-41F3B660A832}” within RSClientPrint.inf.

    11.   Now, unregister the RSClientPrint control.

    12.   Open the custom web application.

    13.   Open a report.

    14.   Print it.

    15.   If the error “Unable to load client print control” occurs, it means the ReportViewer control does not update to latest version.  Please apply “Visual Studio 2005 Service Pack 1 GDIPLUS.DLL Security Update” on the application server.

    16.   Now, I assume we would print report from custom web application server well.

     

    Visual Studio 2005 Service Pack 1 GDIPLUS.DLL Security Update:

    http://www.microsoft.com/downloads/details.aspx?familyid=e186aeed-e9d7-4a02-84b3-bbed116ca060&displaylang=en

     

    If you have any more questions, please feel free to ask.

     

    Thanks,

    Jin Chen


    Jin Chen - MSFT
    • Marked As Answer byPaulino PP Tuesday, November 10, 2009 8:29 PM
    •  
  • Tuesday, November 10, 2009 5:53 AMJin ChenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi Paulino,

    After reviewing your first post, I find the cause is that the RSClientPrint.cab does not update to the latest version.

    To solve the issue, please apply Cumulative update package 6 for SQL Server 2005 SP3. Cumulative update package 5 for SQL Server 2005 SP3 is not good enough.

    By default, if we met the error "Unable to load client print control", we can follow these steps to solve it:
    1.Update the SQL Server to the latest version. Include the cumulative update package.
    2.Update the Server to the latest version, or apply the new hotfix.
    3.Make sure the ReportViewer control is the newest one.
    4.Unregister the RSClientPrint on the client.
    5.Make sure the client has the permissions to install ActiveX.

    For more information, please see:
    http://support.microsoft.com/kb/974648/en-us

    Please feel free to ask, if you have any more questions.

    Thanks,
    Jin Chen

    Jin Chen - MSFT
    • Marked As Answer byPaulino PP Tuesday, November 10, 2009 8:30 PM
    •  

All Replies

  • Saturday, November 07, 2009 5:31 PMhdw Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello Paulino,
    I also spent hours and days on this problem. With my developer machine everything worked fine but on the customer site I had the same problem.
    The reason was, that there are different versions of the RsClientPrint-ActiveX, even though both Versions showed in the Report-Source-Code the same Version string.
    You need to have the right RsClientPrint.cab file which is in the "program files/microsoft sql server/mssql.2/reporting services/reportser/bin" folder (mssql.2 may vary with the number on your machine e.g. mssql.3).
    I copied this file from my machine to customers machine. Thats all. When on the customers side a user uses the printer, the ActiveX-Installation dialog comes up and when you agree to installation you can immediately print.
    My RsClientPrint.cab file shows in file - properties - digital signatures - time stamp: Tue. 25. November.2008 8:31.15 (but I don't know, if this is depending on the Microsoft Version or if this comes from my download date).
    My suggestion is, you look for this version (or write me an email).
    I hope this helps.
    Regards
    Dieter
  • Sunday, November 08, 2009 2:59 PMPaulino PP Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Dieter, I have copied the RSClientPrint.cab files from the report server located at C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\RSClientPrint.cab and put them in a client's PC at c:\WINDOWS\system32 and have had no success
    When it tries to install the client, I look at "C:\WINDOWS\Downloaded Program Files" and find that there is an ActiveX Control with name "{0D221D00-A6ED-477C-8A91-41F3B660A832}" that it shows a Status as "Unknown" instead of "Installed" 
    .
    Paulino
  • Sunday, November 08, 2009 6:11 PMhdw Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Paulino,
    I did the same you did with the downloaded versions, and I had the same results as you have.
    I'm sure you must have the right version and that there ar some minor but important differences between the versions. When I copied the RSClientPrint.cab file from my developer machine to the servers "program files/microsoft sql server/mssql.2/reporting services/reportserver/bin" folder, from where the clients get the ActiveX deliverd, everything worked fine without additional handlings.
    Regards
    Dieter

  • Monday, November 09, 2009 8:46 AMJin ChenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi Paulino,

    All you have done is OK.

    Could you please un-register the RSClientPrint on the client, and then try to print the report again?

    Thanks,
    Jin Chen


    Jin Chen - MSFT
  • Monday, November 09, 2009 12:17 PMTobiasVdb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hey,

    Same problem as the poster, same error.

    Print works when testing with the visual studio development server, but when published, it won't.

    So how do I unregister the rsclientprint on the client? And how can I ask this from all my clients?

    My versions:

    On the server running reportserver:
    rsclientprint.dll 2005.90.4035.0
    reportserver 9.00.4035.00
    reportviewer.dll 9.0.21022.8
                            8.0.50727.1826

    Client computer
    reportviewer 9.0.21022.227
                       8.0.50727.4401

  • Monday, November 09, 2009 3:00 PMPaulino PP Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Jin,
    On the client I've un-registerd the rsclientprint.dll by doing
    C:\Windows\system32\regsvr32.exe /u rsclientprint.dll
    When I try to print again, I get the install software dialog box, then I click "Install"...but I get the same error message "Unable to load client print control."


    Paulino
  • Monday, November 09, 2009 3:02 PMChris Cormier Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Export to PDF and print from there.  Kind of a hack, and you'll have problems with landscape reports, but at least that might get you going for a short time.
  • Monday, November 09, 2009 7:49 PMPaulino PP Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Jin,
    We have an additional question.
    When we explore the RSClientCab trying to be installed in the client PC, we notice is trying to install one that by looking at its RSClientPrint.inf it has CLID = {41861299-EAB2-4DCC-986C-802AE12AC499} with File Version=2005,90,4035,00
    We notcied that it gets installed by looking at C:\WINDOWS\Downloaded Program Files but the name of the Program is not RSClientPrint, but instead is called "{0D221D00-A6ED-477C-8A91-41F3B660A832}" and it shows a Status as "Unknown" instead of "Installed"

    Does this tell anything?


    Paulino
  • Tuesday, November 10, 2009 5:48 AMJin ChenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi Paulino,

     

    From your last reply, I suppose the issue is caused by the RSClientPrint control is not the newest one.

     

    So, please follow these steps to solve the issue:

    1.       Open the Report Server folder.

    By default, the folder is: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer

    2.       Open the sub folder bin.

    3.       Extract the package RSClientPrint.cab

    4.       In the extracted folder, right-click on the rsclientprint.dll, and then click “Properties”

    5.       Make sure the version is “2005.90.4266.0” from the “Version” tab. If the version is less than “2005.90.4266.0”, that means we did not apply Cumulative update package 6 for SQL Server 2005 SP3 successful. Please re-apply it.

    6.       After making sure the RSClientPrint.cab has the newest version.

    7.       Please go the client, open the Report Manager: http://<reportserver name>/reports. Please open the Report Manager, not the custom web application.

    8.       Open any report.

    9.       Click “Print” button.  If the report is printed correctly, it means the RSClientPrint control has been installed correctly on the client.

    10.   In this case, go to “C:\Windows\Downloaded Program Files”, we will see RSClientPrint.dll with version ““2005.90.4266.0”, and CLSID “{0D221D00-A6ED-477C-8A91-41F3B660A832}” within RSClientPrint.inf.

    11.   Now, unregister the RSClientPrint control.

    12.   Open the custom web application.

    13.   Open a report.

    14.   Print it.

    15.   If the error “Unable to load client print control” occurs, it means the ReportViewer control does not update to latest version.  Please apply “Visual Studio 2005 Service Pack 1 GDIPLUS.DLL Security Update” on the application server.

    16.   Now, I assume we would print report from custom web application server well.

     

    Visual Studio 2005 Service Pack 1 GDIPLUS.DLL Security Update:

    http://www.microsoft.com/downloads/details.aspx?familyid=e186aeed-e9d7-4a02-84b3-bbed116ca060&displaylang=en

     

    If you have any more questions, please feel free to ask.

     

    Thanks,

    Jin Chen


    Jin Chen - MSFT
    • Marked As Answer byPaulino PP Tuesday, November 10, 2009 8:29 PM
    •  
  • Tuesday, November 10, 2009 5:53 AMJin ChenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi Paulino,

    After reviewing your first post, I find the cause is that the RSClientPrint.cab does not update to the latest version.

    To solve the issue, please apply Cumulative update package 6 for SQL Server 2005 SP3. Cumulative update package 5 for SQL Server 2005 SP3 is not good enough.

    By default, if we met the error "Unable to load client print control", we can follow these steps to solve it:
    1.Update the SQL Server to the latest version. Include the cumulative update package.
    2.Update the Server to the latest version, or apply the new hotfix.
    3.Make sure the ReportViewer control is the newest one.
    4.Unregister the RSClientPrint on the client.
    5.Make sure the client has the permissions to install ActiveX.

    For more information, please see:
    http://support.microsoft.com/kb/974648/en-us

    Please feel free to ask, if you have any more questions.

    Thanks,
    Jin Chen

    Jin Chen - MSFT
    • Marked As Answer byPaulino PP Tuesday, November 10, 2009 8:30 PM
    •  
  • Tuesday, November 10, 2009 8:37 PMPaulino PP Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Jin,

    The Cumulative Update 6 did the fix.
    We followed steps 1 through 14 succesfully. We are able to print again.
    We did not have to install the security update for Visual Studio 2005 SP 1 GDIPLus.dll

    On the client, we had to delete from c:\Windows\system32 any of the files that we had manually copied from the RSClientPrint.cab at the reporting server.

    Thanks for your help and support. Our more than one hundred users are happy again.
    Please recommend Microsoft to make a different approach to issues like this one. We spent MANY hours with this one.
    Paulino
  • Monday, November 16, 2009 9:55 AMTobiasVdb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hey,

    Still have the problem.

    I followed the steps, first time up until 5.
    Version was outdated so I installed Cumulative update package 6 for SQL Server.

    Once again I followed the steps, passing 5 with success, until 10, where I found an outdated RSClientPrint.dll, I now don't know how to unregister the RSClientControl.

    I tried C:\Windows\system32\regsvr32.exe /u rsclientprint.dll but it gave the following error:

    The module "rsclientprint.dll' failed to load.
    Make sure the binary is stored ath the specified path or debug it to check for problems witht the binary or dependent .DLL files.

    The specified module could not be found.

    What do I do next?

  • Monday, November 16, 2009 2:45 PMPaulino PP Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Tobias,
    The way you are trying to do it is correct. I got the same error and all I did was assume it was not there anymore. So I moved forward to the next step and finally worked out. I hope this helps.
    Paulino
  • Monday, November 16, 2009 4:01 PMTobiasVdb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    So my next logical step would be to install Visual Studio 2005 Service Pack 1 GDIPLUS.DLL Security update?

    Therefore my next question: What if I work with Visual Studio 2008?
  • Monday, November 16, 2009 7:44 PMPaulino PP Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    We did not have to install the security update for Visual Studio 2005 SP 1 GDIPLus.dll in order to make it to work

    Paulino