none
Unable to load client print control

    Question

  • When you display a SQL Reporting Services report to the screen in the header there is a Printer Icon displayed.  When we click this icon we get an error message "Unable to load client print control ".

    Does anyone know what we need to load or what we need to do to resolve this so that we can print the report directly to teh printer, rather than having ot prinnt the web page, which also prints all the Web headre information

    Tuesday, April 04, 2006 7:40 AM

Answers

  • I work in an environment where the users don't have Admin Rights so they can't install the required Active X control.  Here is a great article on pushing it out to the users.

     

    http://www.kodyaz.com/articles/client-side-printing-silent-deployment-of-rsclientPrint.aspx

     

     

    Thursday, September 27, 2007 1:59 AM
  • The Client Print Control is an Active X object. You need to be able to download and install the control. In Internet Explorer\Tools\Internet Options\Security\Custom Level you can find the settings to allow downloading of Active X controls.

     

    Tuesday, April 04, 2006 3:59 PM
    Moderator
  • The SQL 2005 SP1 version of the control has been updated to better handle the versioning of the print control so that you will not have to uninstall and install the control between SQL2000\SQL2005 RTM\SQL2005 SP1

    In regards to Active X controls, my understanding is you can install the control via SMS using the RSClientPrint.cab file that comes with the RS installation. The user will still require the permission to run Active X controls.

     

    Friday, May 05, 2006 9:23 PM
    Moderator
  • It is automatically installed when you click the print button when viewing a report.
    Wednesday, September 13, 2006 6:16 PM
    Moderator

All replies

  • The Client Print Control is an Active X object. You need to be able to download and install the control. In Internet Explorer\Tools\Internet Options\Security\Custom Level you can find the settings to allow downloading of Active X controls.

     

    Tuesday, April 04, 2006 3:59 PM
    Moderator
  • We are facing the same problem. Advising the clients who use our web application to weaken the security of their Internet Explorer is not really an option. Can the ActiveX control be downloaded separately?

    Kind regards,

     

    Martijn Bakker

    Tuesday, April 18, 2006 8:43 AM
  • I'm having the same problem as described above. What is the solution?
    Friday, May 05, 2006 4:32 PM
  • I would like to throw one other issue we have found with the print control.  If a user has previously installed the RS 2000 print control, and tries to print a report in 2005 it will error out.  You have to manually remove the old activeX control from the users PC (C:\WINDOWS\Downloaded Program Files) and rerun the report to get the new control.  Also, the 2005 from our experience doesn't seem to work with 2000 either.
    Friday, May 05, 2006 4:40 PM
  • The SQL 2005 SP1 version of the control has been updated to better handle the versioning of the print control so that you will not have to uninstall and install the control between SQL2000\SQL2005 RTM\SQL2005 SP1

    In regards to Active X controls, my understanding is you can install the control via SMS using the RSClientPrint.cab file that comes with the RS installation. The user will still require the permission to run Active X controls.

     

    Friday, May 05, 2006 9:23 PM
    Moderator
  • What is the process to install the ActiveX if we don't have SMS?
    Tuesday, September 12, 2006 7:37 PM
  • It is automatically installed when you click the print button when viewing a report.
    Wednesday, September 13, 2006 6:16 PM
    Moderator
  • Of course we know it's supposed to but we also know that things don't always work as they're supposed to.  In my case, I have at least one system where it doesn't download automatically.

    I've seen postings where others mention installing the AcitiveX manually.  I'm looking for details on how that is done.  I can see the .cab file on the report server but need to know what to do to get it installed on the client.

    Any help is of course appreciated.

    Jon
    Friday, September 15, 2006 2:20 AM
  • I get the same message and it does not install. I tried setting IE to prompt for signed or unsigned ActiveX controls but it still doesn't work. But this machine is weird - it won't take Windows Updates either, I have to install them while shutting the machine down. Still, I'd like a way to install that control manually.
    Wednesday, September 20, 2006 3:37 PM
  • To manually install the .CAB file:

    1. Download the .cab file and save it on your desktop.
    2. After the file is saved on your desktop, right-click the Iuctl.cab file, and then click Open
    3. Select all the files that are listed. To do this, point to the file list, and then press CTRL+A.
    4. Right-click the files that you selected, and then click Extract.
    5. Select a known location, and then click OK. For example, select the desktop. 
    6. Locate the file where you extracted it. For example, locate the file on the desktop.
    7. Right-click the RSClientPrint.inf file, and then click Install.

    Tuesday, October 10, 2006 11:19 PM
  • I just tried that. I found the cab somewhere under programs/Microsoft sql server. But when I extracted it and tried Install, it just blinked. In trying to print from RS I got the usual Unable to load Client Print Control.

    But, as I know, this machine is a bit weird about activex controls so I'm not taking it personally.

    Wednesday, October 11, 2006 4:01 PM
  • In a perfect world yes the ActiveX Print Control for Reporting Services will be installed on the client's machine.  However in an environment such as the one I manage our Desktop Users DO NOT have Local Administrator rights and the ActiveX Installation fails and "Unable to load client print control" is displayed on their screens.

    Besides SMS is there any other option to silently install the the ActiveX Print Control on the PCs for users without admin rights?

    • Proposed as answer by Sumeet_amigo Tuesday, February 03, 2009 5:05 PM
    Monday, October 16, 2006 8:26 PM
  • The SSRS activeX control is no different then any other web AX control. You will always need admin rights to install it.

    If you are in a controlled environment (like a Gov't one), then there is usually a method whereby the admins push out updates to the users.

    You could always use the cab file and create an install program in .Net and have them push it out.

    Other then that, you are kinda s.o.l. 

    If your computer won't take MS updates then installing an AX control is the least of your worries, and once you fix the first problem, the second should fix itself.

     

    Daryl

    Monday, October 16, 2006 8:39 PM
  • I am still operating under SQL Server 2000.  I couldn't find RSClientPrint.cab in the Microsoft SQL Server folder. 

    Will I be able to print this report without upgrading to 2005?  I need this report before the time it would take to implement an upgrade.

    Thanks.

    • Proposed as answer by Junaidyit Wednesday, August 03, 2011 9:26 AM
    Wednesday, February 07, 2007 7:59 PM
  • Hi

    Regarding the load client print control

    How to programatically set the securtiy option with out manually setting the option for downloading the Active X controls.

    Because i cannot see whether the option is set or not.If the option is not set then i will get the error..

    thanks in advance

     

    Friday, August 17, 2007 11:35 AM
  • I work in an environment where the users don't have Admin Rights so they can't install the required Active X control.  Here is a great article on pushing it out to the users.

     

    http://www.kodyaz.com/articles/client-side-printing-silent-deployment-of-rsclientPrint.aspx

     

     

    Thursday, September 27, 2007 1:59 AM
  •  

    Run IE as an administrator and go to the link the user is attempting to print from. It then should prompt for an active X install and just right click and following the directions. I actually just performed this on a workstation and it worked.
    Monday, September 08, 2008 9:37 PM
  • Is there any other way Instead of running .Cab and Admin rights.

     

    I am planning to execute at the End User.

     

    Thanks,

    Prabu

    Thursday, October 09, 2008 2:52 PM
  • A lot of our users just now started complaining of this issue...it appears it may be related to a windows update of some sort.  Earlier today I was prompted to install the activex control, but after installing the latest windows updates I don't get the prompt anymore, only the message box stating "Unable to load client print controls".  Anyone else noticing this problem?

    Wednesday, October 15, 2008 10:43 PM
  • You may want to check out this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=4006172&SiteID=1

     

    Alex.

    Wednesday, October 15, 2008 11:13 PM
    Moderator
  • Just now got off the call with Microsoft personnel. we tried several combinations but the one that finally worked is just installing the Cumulative Update 9 for SQL Server 2005 on the server machine. Once this is done all the clients that try to print will be prompted to install the new Active X control and then print is working fine.

    While uninstalling the patch KB956390 also works the above solution is better as it has to be done only at the server.

     

    Hope this helps all who are facing this issue.

     

    Thursday, October 16, 2008 6:52 PM
  • We have the problem as well, only it just started happening.  The same users/computers/browsers that could print last week  now can't all of a sudden.  The report we're trying to print is only a single page.

    Regards,
      Joel

    Friday, October 17, 2008 5:54 PM
  • I am using SQL Server 2005 SP1/ Windows 2003 Server Ent.

     

    Is there anyway to get the print button to work?  For people who are local admin and for those who are not?

    Monday, October 20, 2008 3:41 PM
  •  

    You can remove the two new updates Microsoft released yesterday. Go to Control Panel, Add/Remove Programs. Check the Show Updates box. Locate the Security Updates KB956803 and KB956391, and remove one at a time. After the removal you will have to restart the computer. You should be able to print.

     

    Windows XP

    Security Update for Windows XP (KB956803)

    Thursday, October 16, 2008

    Automatic Updates

    Windows XP

    Cumulative Security Update for ActiveX Killbits for Windows XP (KB956391)

    Thursday, October 16, 2008

    Automatic Updates

     

    Monday, October 20, 2008 4:46 PM
  • Hi Ryan,

     

    You can install the server GDR patch for Reporting Services SP1. If you run Microsoft Update(not Windows Update) on your server, the patch should be in the list of patches to install. Once you have that patch installed, your clients should be able to print again. If not, please ping me at bradsy@removememicrosoft.com.

     

    Monday, October 20, 2008 6:26 PM
    Moderator
  • Hi Brad,

     

    Do you have a link for that patch?  I'm having problems locating it.

     

    Thanks,

     

    Joe

     

    Monday, October 20, 2008 7:22 PM
  • Brad,  I am having the same problem as of last week this broke for my custom asp.net web app.     I have tried the updates on the server along with all the other sugestions without luck.

     

     

    I am using the 2008 Report viewer running in local report mode only.

     

     

    Tuesday, October 21, 2008 1:32 AM
  • I take back my last post, the server update did fix the problem,  I had to manually restart the SQL server service.   I couldnt do it right away as this was a production box.   thanks.

     

    Tuesday, October 21, 2008 2:55 AM
  • I work with Ryan and I'll add to his post.  Our installation has been up and running for several months in production, but people have only recently needed to try to print any of the reports and they are getting errors because they cannot because they are being prompted to install an AX control.  Based on everything I have read in this thread so far, our issue is not with the server, but is related to security policies within the user's browser.

    Without going in to the layers of our organization and the multiple security policies in our environment, let me sum up and say that handing out Local Admin isn't an acceptable option.   We may be able to distribute the .cab file for local installation, although it is not clear from this thread if that will solve the problem.  Alternatively, we may be able to add the site to a trusted zone that is configured to execute AX controls.

    Are there any other options for being able to use this feature?

    Thanks,

    David Modlin
    Tuesday, October 21, 2008 9:50 PM
  • So I applied all updates available today and then rebooted both the SQL and Terminal Server.

    On the Terminal Server (2003 Server) that I'm getting the Error.

     

    I've Logged in as a Domain & Local Admin and tried to view the report and I also get the Error.

     

    If I do it on my local machine (Vista x64), I get Prompted to install the Active-X Control and all is good in the World

     

    I've made sure that the all the Active-X Related Security settings were enabled. (IE Complained I was 'at risk')

     

    It’s a Production system, so I can't just install/remove patches on the two servers and reboot them.

     

    I've also copied the RSClientPrint.cab file to the Terminal Server, then extracted it to a folder and right clicked on the .inf and did the Install.  Nothing changed.

     

    I removed the update KB956390, though have not been able to reboot yet.

     

    Any other Suggestions?

    Wednesday, October 22, 2008 4:49 PM
  • thank you so much...this actually worked for me as those updates were part of XP SP3 which I happened to install...you are the man!!
    Wednesday, October 22, 2008 6:37 PM
  • Yes, I am getting the same problem, I am not getting the prompt anymore for "install active X control". Please help if any body knows the solution. I am unable to print from Report Manager. getting the same error "unable to load client print control"

     

    Thanks in advance

     

    bsembhi@gmail.com
    Friday, October 24, 2008 2:52 PM
  • All I did was apply all outstanding Hotfixes for my SQL server box, that resolved the issue.    You do need to restart the services if you dont reboot.    I didnt have much faith that it would resolve the problem but it did fix it.

    Friday, October 24, 2008 2:58 PM
  • While we had applied CU9 to our servers, it still didn't help. What finally worked for us was to Download the Microsoft Report Viewer Redistributable 2008 and run the ReportViewer.exe on the server http://www.microsoft.com/downloads/details.aspx?familyid=CC96C246-61E5-4D9E-BB5F-416D75A1B9EF&displaylang=en and then update our web pages to use the 9.0.0.0 version of the webform. Users are then either prompted or not based on the security settings but we were just happy to get it to "take" the updated version of the print control. http://billfellows.blogspot.com/2008/10/unable-to-load-client-print-control.html
    Saturday, October 25, 2008 4:08 AM
  • I faced this same issue which coincided with the Automatic Update installation of Security Update KB956351 for Windows XP.

    I opened a case with Microsoft Support and this is the solution provided that worked for me-

    You can either uninstall this update, which should fix this issue, or apply a few patches for SSRS 2005 SP2.

    You may need to delete the RSClient Print Control which is typically in C:\WINDOWS\Downloaded Program Files\.

    I installed Cumulative Update 10 for SQL Server 2005 SP2 as well as
    the GDR fixed version of the ReportViewer control. After that you may need to restart services or reboot. You can get the fix for the version of the control being used from the links below.

    ReportViewer 2005 SP1:

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



    Saturday, October 25, 2008 7:22 PM
  • We have released an updated SharePoint add-in that addresses the client print problem for English customers.  We are providing English immediately and are working to release all localizations of the SharePoint Add-in as soon as possible.

     

    Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies Download Page:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=1e53f882-0c16-4847-b331-132274ae8c84&displaylang=en

     

    To use this version of the Reporting Services Add-in, the SQL Server Reporting Services server deployment used in conjunction with the Reporting Services Add-in must be patched with the updates listed under Microsoft SQL Server in Microsoft Security Bulletin MS08-052.

     

    Thanks,

    -Lukasz

     

    lukaszp@removemeMicrosoft.com

     

    Monday, October 27, 2008 5:16 AM
    Moderator
  • Do I do this on the server or each client machine?
    Tuesday, October 28, 2008 3:32 PM
  •  

    My clients are able to use the print icon now by removing the updates you have suggested to remove.  Thank you.
    Tuesday, October 28, 2008 8:43 PM
  •  stevejonesforrent wrote:
    I faced this same issue which coincided with the Automatic Update installation of Security Update KB956351 for Windows XP.

    I opened a case with Microsoft Support and this is the solution provided that worked for me-

    You can either uninstall this update, which should fix this issue, or apply a few patches for SSRS 2005 SP2.

    You may need to delete the RSClient Print Control which is typically in C:\WINDOWS\Downloaded Program Files\.

    I installed Cumulative Update 10 for SQL Server 2005 SP2 as well as
    the GDR fixed version of the ReportViewer control. After that you may need to restart services or reboot. You can get the fix for the version of the control being used from the links below.

    ReportViewer 2005 SP1:

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



     

    Was this installed on the Report Server or the local machine having the problem?

    Tuesday, October 28, 2008 10:37 PM
  • Web Server is patched up to date
    Client machine is patched up to date
    Sql server is patched up to date.
    Sql server 2005 is patched up to date.
    ReportingServicesWebUserInterface.dll is version 9.0.3073.0
    Microsoft.ReportingServices.Diagnostics.dll is version 9.0.3073.0

    On web control, register of viewer is <%@ Register TagPrefix="rsweb" Namespace="Microsoft.Reporting.WebForms" Assembly="ReportingServicesWebUserInterface" %>

    In web.config httphandler is <add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, ReportingServicesWebUserInterface, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/>

    webapp compiles without error but when I try to set parameters like
    rvPrintRequestClientReport.LocalReport.ReportPath "mypath\myReport.rdlc"
    app fails with "The method or operation is not implemented"

     

    I would like to use this viewer in the future without the following hacks to fix issue:

     

    Registry hack - If you change the "Compatibility Flags" value to 0, the error goes away.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{FA91DF8D-53AB-455D-AB20-F2F023E498D3}]
    "Compatibility Flags"=dword:0x00000000 (0)
    "AlternateCLSID"="{41861299-EAB2-4DCC-986C-802AE12AC499}"

     

    Removal of two security updates that cause the issue KB956391, KB954593

     

    How do I update my dev box/reference the new control?

     

    Wednesday, October 29, 2008 1:12 PM
  • Hi,

    I tried the fix.I installed the (KB954765) and Reome the RSClient Print Control from  C:\WINDOWS\Downloaded Program Files\.

     

    Still it is not working andf I have the User who is not having rights in C:.My End user is unable to save/run any program which affect  C:.

     

    How can I resolve this.

     

    Thanks,

    Prabu

     

    Wednesday, October 29, 2008 2:09 PM
  • Removing the update KB956803 solved the issue for us, thanks!!
    Wednesday, October 29, 2008 5:00 PM
  • I need to update my blog with how we finally corrected it using the 8.0.0.0 version of the report view control but it boiled down to performing the following steps on the IIS/reporting server box

     

    1)  Install CU 9

    2)  Uninstall the existing ReportViewer.exe

    3)  REBOOT (missed this one)

    4)  Install the service packed, hotfixed version of the ReportViewer 2005 (http://www.microsoft.com/downloads/details.aspx?FamilyID=82833f27-081d-4b72-83ef-2836360a904d&DisplayLang=en)

     

    Doing the above steps has allowed our users to have the infamous killbit KB applied and still print from embeded reports.

    Thursday, October 30, 2008 1:59 PM
  • Removing update KB956391 fixed the problem here.

     

    Thx a lot

    Monday, November 03, 2008 9:21 AM
  • Hi All,

    I came across this error in our network last week and managed to sort it out by uninstalling the following two updates from Microsoft.


    KB954606
    KB956391

    Hope this helps.

    Thanks,

    Aash.


    Monday, November 03, 2008 11:23 AM
  • We were also experiencing this issue with our users. In a test box, I removed the following registry key (backed it up first of course):

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{FA91DF8D-53AB-455D-AB20-F2F023E498D3}]
    "Compatibility Flags"=dword:0x00000000 (0)

     

    The problem is that this would have to be done on the client PCs. Our temporary fix is have the LAN team manually install the ReportViewer.exe when users call in.

     

    Thanks,

    Nuno

     

    Monday, November 03, 2008 4:27 PM
  • Anyone has any progress on this case? So far the temporary solution is uninstalling the specified KB...
    Thursday, November 06, 2008 9:23 PM
  • We have managed to keep the KB and have the print control work. 

     

    We applied the following steps on our reporting server

     

    1)  Install CU 9

    2)  Uninstall the existing ReportViewer.exe

    3)  REBOOT (missed this one)

    4)  Install the service packed, hotfixed version of the ReportViewer 2005 (http://www.microsoft.com/downloads/details.aspx?FamilyID=82833f27-081d-4b72-83ef-2836360a904d&DisplayLang=en)

    Thursday, November 06, 2008 9:30 PM
  •  Charles Talleyrand wrote:

    4)  Install the service packed, hotfixed version of the ReportViewer 2005 (http://www.microsoft.com/downloads/details.aspx?FamilyID=82833f27-081d-4b72-83ef-2836360a904d&DisplayLang=en)

     

     

    Note to Step 4, you may need the ReportViewer 2005 SP1 and/or ReportViewer 2008 SP1 hotfix depending .  I applied the Microsoft Report Viewer Redistributable 2005 Service Pack 1 yesterday and today discovered an "Unable to load client print control" error on a recently deplyed 2008/.net 3.5 site while an older .Net 2.0 report viewer running correctly.    Applying both patches fixed all print popup issues.

     

    4a) Microsoft Report Viewer Redistributable 2005 Service Pack 1

    verify version by checking the source html of a test report and see if it contains

    "/Reserved.ReportViewerWebControl.axd" and "Version=8.0.XXXXX"

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

     

    4b) Microsoft Report Viewer 2008 SP1 Redistributable

    verify version by checking the source html of a test report and see if it contains

    "Reserved.ReportViewerWebControl.axd?" and "Version=9.0.XXXXX"

    http://www.microsoft.com/downloads/details.aspx?FamilyID=bb196d5d-76c2-4a0e-9458-267d22b6aac6&DisplayLang=en

     

    5) restart IIS (iisreset) or server

     

     

    As Charles mentions, this fixes the "Unable to load client print control" issue without removing the KB patch or modifying the client registry. 

     

    Additional info gathered here, Rahul's comment:

    http://www.technologystudio.net/blog/post/Microsoft-Update-KB956391-breaks-Reporting-Services-ReportViewer.aspx

     

    • Proposed as answer by Emil Roshan Friday, October 30, 2009 8:32 AM
    Friday, November 07, 2008 7:19 AM
  •  

    Hi everything worked great on my development box(32 bit(, now I am able to use print button, but when I try to update the 64 bit production servers, I still see this problem, is there anything that I am missing?

     

    Erinc

    Thursday, November 20, 2008 10:18 PM
  • Thank you, it worked just fine!
    Tuesday, December 16, 2008 9:14 PM
  • Charles Talleyrand said:

    We have managed to keep the KB and have the print control work. 

     

    We applied the following steps on our reporting server

     

    1)  Install CU 9

    2)  Uninstall the existing ReportViewer.exe

    3)  REBOOT (missed this one)

    4)  Install the service packed, hotfixed version of the ReportViewer 2005 (http://www.microsoft.com/downloads/details.aspx?FamilyID=82833f27-081d-4b72-83ef-2836360a904d&DisplayLang=en)


    Panod Klongtruatroke said:

     Charles Talleyrand wrote:

    4)  Install the service packed, hotfixed version of the ReportViewer 2005 (http://www.microsoft.com/downloads/details.aspx?FamilyID=82833f27-081d-4b72-83ef-2836360a904d&DisplayLang=en)

     

     

    Note to Step 4, you may need the ReportViewer 2005 SP1 and/or ReportViewer 2008 SP1 hotfix depending .  I applied the Microsoft Report Viewer Redistributable 2005 Service Pack 1 yesterday and today discovered an "Unable to load client print control" error on a recently deplyed 2008/.net 3.5 site while an older .Net 2.0 report viewer running correctly.    Applying both patches fixed all print popup issues.

     

    4a) Microsoft Report Viewer Redistributable 2005 Service Pack 1

    verify version by checking the source html of a test report and see if it contains

    "/Reserved.ReportViewerWebControl.axd" and "Version=8.0.XXXXX"

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

     

    4b) Microsoft Report Viewer 2008 SP1 Redistributable

    verify version by checking the source html of a test report and see if it contains

    "Reserved.ReportViewerWebControl.axd?" and "Version=9.0.XXXXX"

    http://www.microsoft.com/downloads/details.aspx?FamilyID=bb196d5d-76c2-4a0e-9458-267d22b6aac6&DisplayLang=en

     

    5) restart IIS (iisreset) or server

     

     

    As Charles mentions, this fixes the "Unable to load client print control" issue without removing the KB patch or modifying the client registry. 

     

    Additional info gathered here, Rahul's comment:

    http://www.technologystudio.net/blog/post/Microsoft-Update-KB956391-breaks-Reporting-Services-ReportViewer.aspx

     


    Thank you both for your posts!!  I was having a LOT of trouble with this problem of users receiving the error "Unable to load client print control" and originally fixed by uninstalling windows update KB956391.  I was able to use this solution because only a few users used the report server.  Then the error came back, and I solved it on a few computers by uninstalling KB960715, but it did not fix it on all workstations.  Then, we needed to release a new report to ALL of our users, so I needed to find a solution fast!  It would have been an extremely tedious task to try and find the windows updates that were causing the problem on every user's computer, uninstall them, and then hide them from automatically installing again.

    Well thanks to you guys, I got it working by installing a couple patches ONLY on the Report Server!  I followed Charles' instructions of installing SQL 2005 Cumulative Update 9 from here . Then I downloaded the 2008 Report Viewer Redistributable.  After uninstalling the 2005 Report Viewer Redist. from the Report Server, installing the Cumulative Update 9 on the Report Server, and installing Report Viewer 2008 Redist. on the Report Server, it is working on all workstations, even after I reinstalled KB956391 AND KB960715!

    Thanks a lot for the help!
    Friday, February 20, 2009 3:19 PM
  • Thanks. by removing those two updates and having rebooted now it prompts for installing AX controll.
    then once i clilck on print icon it comes up with Unable to load client print control

    next i will be checking log to find if AX installed properly.

    cheers
    • Proposed as answer by dotnettrio Tuesday, April 21, 2009 11:00 PM
    Monday, March 16, 2009 12:33 AM
  • I have had the same problem (on several different servers). Applying SP3 and Report Viewer SP1 has helped on some of the servers, allowing the client machines to connect and download the control with no problem.
    However, I have had one server that, even after applying the updates, when accessing the report viewer using a client machine, it was still giving me the error.
    On looking into the exact URL GET request that is being sent, I discovered that it is possible to force the client machine to connect directly to the Report Server to download the control.

    The user would need to enter the following url:

    http://reportservername/Reports/Reserved.ReportViewerWebControl.axd?ReportSession=51bjqv45xydgos2wghu5ceza&ControlID=7617dedbf0234f89b80cad8e64431014&Culture=2057&UICulture=9&ReportStack=1&OpType=PrintHtml


    This should then pop up the required download/install prompt.

    Please can people let me know if this works on their systems as well
    Wednesday, April 22, 2009 8:50 AM
  • Did You get a message warning you that other programs might not work if you remove that hotfix? I got this looooong message about all the stuff that could break if I uninstalled the hotfix.
    DJ Baby Anne's Biggest Fan................
    Wednesday, April 29, 2009 3:49 PM
  • I tried to follow Paul_IRET's steps.  But for step 2, how to uninstall the existing reportviewer.exe ?
    Thursday, May 07, 2009 9:29 AM
  • You can extract the cab file and save it to a network share

    then run a .bat file on all workstations (via startup script) to copy extracted files to system32 and regiter rsclient print with registry

    here is an example startup script

    @echo off

    rem #############################################################
    rem Intall ActiveX to print from reporting service -
    rem Copy active x files to target machine's system32
    rem register with registry
    rem ##############################################################

     

    xcopy "\\replacewithservershare\gdiplus.dll" "C:\WINDOWS\system32\*.*" /y
    xcopy "\\replacewithservershare\RSClientPrint.dll" "C:\WINDOWS\system32\*.*" /y
    xcopy "\\replacewithservershare\RSClientPrint.inf" "C:\WINDOWS\system32\*.*" /y

    rem you get the picture - rest of the extracted files

    rem register with os
    regsvr32.exe /s c:\windows\system32\rsclientprint.dll

    this methode install and regiter rsclient print even before user log on hence doesnt matter who logs in. catch is you will have to run it for a week or so and stop the startup script

     

    • Proposed as answer by Abercrombie07 Thursday, May 14, 2009 7:50 PM
    Thursday, May 14, 2009 5:27 AM
  • Good 'ol login script.......
    I've been doing database and application stuff too long.............
    Thx Emil..
    DJ Baby Anne's Biggest Fan................
    Thursday, May 14, 2009 7:50 PM
  • We are having the same issue about loading the print control on user machines and we would like apply CU9 on the server where SSRS is installed. But we are little confused. Do we need to run all the 5 files in the CU 9 download or just first 4. 

    SQLNCLI
    SQLServer2005_ADOMD
    SQLServer2005_ASOLEDB9
    SQLServer2005_XMO
    Yukon_SP2_CU9

    Please help.

    Thank you.


    madduri
    Monday, June 29, 2009 4:54 PM
  • I work in an environment where the users don't have Admin Rights so they can't install the required Active X control.  Here is a great article on pushing it out to the users.

     

    http://www.kodyaz.com/articles/client-side-printing-silent-deployment-of-rsclientPrint.aspx

     

     


    This is a right answer for me.
    support and search
    Tuesday, August 04, 2009 9:18 PM
  • Very useful forum.

    -Bob
    http://www.crossloop.com/BobHartung
    Saturday, August 15, 2009 3:42 AM
  • Question:

    I have the same problem as everyone else, but I am a local admin on my machine and even if I put all activeX to promt I don't get a promt before the error message "Unable to load client print control" fires.

    The other part of my problem is that I do this on my developer machine where I have app-server, sql-server and web-server locally.
    I start IE and start my local application.
    Then it works fine, I can print without problems.

    THEN, when I use my developer machine against the test server where the application- and web-server resides, the sql server is a separate server in this case. Then it fires the error message "Unable to load client print control". I find this a bit strange.
    I use the IE on my local machine and use the url of my test server.
    Should not the activeX have been installed when I run locally ?? If it is the ActiveX why does it try to install it again, unless it is another version which I'm pretty sure it isn't.

    I can't figure out why I get this problem. Can anyone offer some help or advice here ?
    Wednesday, August 19, 2009 1:55 PM
  • Question:

    I have the same problem as everyone else, but I am a local admin on my machine and even if I put all activeX to promt I don't get a promt before the error message "Unable to load client print control" fires.

    The other part of my problem is that I do this on my developer machine where I have app-server, sql-server and web-server locally.
    I start IE and start my local application.
    Then it works fine, I can print without problems.

    THEN, when I use my developer machine against the test server where the application- and web-server resides, the sql server is a separate server in this case. Then it fires the error message "Unable to load client print control". I find this a bit strange.
    I use the IE on my local machine and use the url of my test server.
    Should not the activeX have been installed when I run locally ?? If it is the ActiveX why does it try to install it again, unless it is another version which I'm pretty sure it isn't.

    I can't figure out why I get this problem. Can anyone offer some help or advice here ?

    We are experiencing the very same problem.  We can print the report from the web page where the SSRS report viewer control lives, fine, if I'm running it against my local IIS.  However, if I then copy the website to our Windows Server 2003 R2 environment, run the ASP.NET app from the server, view the report (just fine, thank you) but then try to print the report I get this "Unable to load clinet print control" error.  The only difference is where I'm running the ASP.NET app from, because it is the same app, since I just copied it from my development machine to the server.  Because I'm running it on my machine, and I've got administrative privileges on my machine and on our network, I don't believe that is the issue.

    I'm using VS 2008.

    Rod
    Thursday, August 27, 2009 7:54 PM
  • Hi Aash2,


    Hi All,

    I came across this error in our network last week and managed to sort it out by uninstalling the following two updates from Microsoft.

    KB954606
    KB956391

    Hope this helps

    Do we need remove these updates from the server where Reporting services has installed or each individual user's machine??

    We have SQL Server 2005 x64 with SP3

    thanks
    Wednesday, September 23, 2009 11:51 PM
  • Any help plz..
    • Proposed as answer by a___ Johnny ___ Thursday, October 29, 2009 12:09 PM
    Thursday, October 01, 2009 10:48 PM
  • Got this silly problem again on a newly built server. Unfortunately removing mentioned two updates didnt fix this time,

    What I followed this time was

    1) removed both updates
    2)removed report viewer(i have app and db on seperate servers and i removed it from both servers)
    3)reboot - important (first attempt without reboot did not work)
    4)installed  Microsoft Report Viewer 2008 SP1 Redistribution on both servers

    follow above steps to figure out the version of RV you are serving to clients.

    once tested report viewer and print dialogue box prompt, installed updates removed previously. Print control continue to work.

    thanks
    Emil
    Friday, October 30, 2009 8:32 AM
  • All,

    There seems to be various solutions and it seems issue is still prevalent. In my case, we followed RSClientPrint.dll installation on users system. We have a distributed set-up and have a seperate Reporting server. Can anyone confirm if removing the updates and installing Microsoft Report Viewer 2008 SP1 Redistribution on Reporting server will work? It is URGENT and need your support.

    Thanks
    Thanks
    Tuesday, November 10, 2009 6:02 AM
  • Yes, can confirm below steps did resolve the issue this time... funny enough I have had three times the same problem and three diffrent solutions, all in this thread, that is proven to be working .

    1) removed both updates
    2)removed report viewer(i have app and db on seperate servers and i removed it from both servers)
    3)reboot - important (first attempt without reboot did not work)
    4)installed  Microsoft Report Viewer 2008 SP1 Redistribution on both servers
    Tuesday, November 10, 2009 6:16 AM
  • Dear Emil,
    Thanks for quick response.

    I didn't have the following patches on the system:

    ·         KB954606
    KB956391

    So, I jumped to http://www.microsoft.com/downloads/details.aspx?familyid=82833F27-081D-4B72-83EF-2836360A904D&displaylang=en and installed Microsoft Report Viewer 2008 SP1 Redistribution.
    Now I can see a small change. It is now prompting to install ActiveX. When I click on Install nothing happens and after 2-3 sec, I get the same message "Unable to load client Print control"

    Please help

    Thanks
    Tuesday, November 10, 2009 9:05 AM

  • Do not remove any kill bits. Just install the Microsoft Report Viewer 2008 SP1 Redistribution on your application server (NOT the report server or NOT the SQL Server) and make sure you have SQL Server 2005 SP3 applied.
    Saturday, November 14, 2009 12:07 AM

  • Do not remove any kill bits. Just install the Microsoft Report Viewer 2008 SP1 Redistribution on your application server (NOT the report server or NOT the SQL Server) and make sure you have SQL Server 2005 SP3 applied.

    Samnalla, after you installed Microsoft Reportviewer 2008 SP1 redistribution on the application server....did your clients still get prompted to install the Active X Control? or does the Active X control get installed automatically? even if the users are not local admin to their computers?

    I need a solution that doesn't require the users to install anything (as they are not administrators).... or my techs to push any file to the client machines and register dlls.... or my techs to change any registry keys or unistall anything...

    Anybody else has solved this problem just at the server level? maybe modifying the applications? My apps are Framework 2.0...  My sql server is 2005 SP3. My Report viewer has the 2005 SP1 redistributable patch.

    anyone?
    Thursday, November 19, 2009 9:16 PM
  • Charles Talleyrand,

    Perfect, but are your users till being prompted to Install the Active X? or they don't have to install anything? are your users local admins?

    Thanks
    Friday, November 20, 2009 6:37 PM
  • Awesome. Thanks Panod.... but are your users being prompted to install the Active X control? or they don't have to install anything anymore? are they local admins?

    Thanks
    Friday, November 20, 2009 6:40 PM
  • Awesome. Thanks Paul_Iret.... but are your users being prompted to install the Active X control? or they don't have to install anything anymore? are they local admins?

    Thanks
    Friday, November 20, 2009 6:45 PM
  • Samnalla is right, it's not a good idea to remove any killbits patches.

    For those of you that only have SQL Server 2005 SP2 applied on your report server, make sure you apply KB970895 or KB970896 (see http://www.microsoft.com/technet/security/bulletin/MS09-062.mspx for appropriate version.)

    Then install Microsoft Report Viewer 2008 or ReportViewer 2008 SP1 on your application server.

    Monday, December 14, 2009 2:13 PM
  • hi HandyManny,

    In our organization, the users are Administrators to their workstations. So they did not
    prompt to install the Active X control? or they don't have to install anything anymore.

    It's just opens the print

    thanks
    Monday, December 14, 2009 11:08 PM
  • Hi all, we are having similar problem receiving the 'unable to load client print controls' msg.

    we upgraded ie from version 6 to version 8 and now receive the above msg when trying to report from reporting services. Uninstalling IE 8 and  re installing IE 6 and we still get the unable to print msg when tring to print from reporting services.

    workstation os is xp 
    server is win 2003 running iis and sqlserver 2005 sp2 we do not have the hotfix XP (KB956391)
    installed. IE is configure to allow active x and to prompt for install.

    Any help appreciated.
    Sunday, February 21, 2010 10:43 PM
  • Hi All

    sorry,my English is not  that good!!

     

    i`m problem with Reporting service!!!(wonderfull!!)

    i`m work with windows server2003 sp2,sql server2005 sp2,and work with reports with client and server.

    but:

    1.i can not print:unable to load client print control

    i know this is ActiveX control,but not install in some clients(and sometimes in server,too!)

    so,remove KB97...(that 2numbers)

    security>custom level is medium

    Rsclientprint (inf file vervion is 2007) is ok

    but in c:/Window>downloaded program files ,version of clientprint is 2005 while i registered that file with SrvReg32.exe!!!

    after the publishes report in server and test print some report is ok but i have dynamic report that with click in field go to another reports ,so that new report not print!!

    2.i want deploy reports on servers but no in localhost

    my question :only deploy on  http://....? but or www....?

    3.so for pass print , my report exported in pdf

    now,i see pdf ,this is OK(font ,style,...) but when print from pdf ,config fonts!!!

    i`m sad,and depress!!!

    can i help me anyone?

    no idea?

    : (

     

    Sunday, April 18, 2010 11:47 AM
  • Thanks Panod , ya it is really a bug with Reporting Service 2005 /2008 dlls , Yes but using 2008 Redistributable i got the success to print smoothly .

    I think it is also needed to restart the IIS also .

    But one issue still left : "I am not able to see the print logo(option) in FF and Chrome browsers" .


    Friday, July 02, 2010 9:41 AM
  • Here is a solution that worked for me: just remove a registry entry (client side!)

    http://vettekerry.wordpress.com/2009/05/04/unable-to-load-client-print-control-in-reporting-services-2005/

    Hope it helps!

    Friday, September 17, 2010 12:02 PM
  • Thanks Ruud007, I removed the registry entry, worked instantly.

    [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{FA91DF8D-53AB-455D-AB20-F2F023E498D3}]

     

    Thursday, October 07, 2010 2:42 PM
  • Our Server environment : SQL2008 x64 SP2 Reporting Services on Windows Server 2008 x64,

    Client PC environment: Windows XP SP2 with IE6 or higher, all users are login to Active Directory, users are not members of local Administrator or power user group.

    Error: When a user printing a report  getting an error as "Unable to load client print control"

    Solution that work for us: replace following files in sql 2008 with SQL 2008 R2

    Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\bin
    RSClientPrint-x86.cab
    RSClientPrint-x64.cab
    RSClientPrint-ia64.cab

    Once you replace files on server side users wont get above error but it is required to do one time installation of this Active X component as a local Administrator or power user. If you are having large number of computers running on Active Directory environment you may create a MSI file with rsclientprint.dll and deploy using AD or SMS. Also I'm  recommending to add report server URL as a trusted site (add to Trusted sites) via Active Directory GP.

    Hope this will help for somebody to sort out this "hectic" problem. We had very tough time to find out a proper solution for this "bug".

    Nishan

    -Sri Lanka-
    Thursday, March 24, 2011 3:59 PM
  • I had this same problem for a very long time. What worked for me was to do the Cumulative Upgrade 9 for SQL Server 2005 (CU9). Next I had to go to the clients we wanted to print from and log in as the administrator, since we do not give those operators administrative properties. Logged in as the admin, you need to go into the security of your web browser (probably internet explorer) and trust the site that hosts your reports on the report server AND enable or ask for all active X. Then go to your report through the web browser and install the active X plug in by clicking the print button. Once this is done, log back into the operator and the plug in is there. IT WORKED. This took me so long to figure out, but I found my solution and figured I would pass it on.

    What did NOT work for me: manually copying the .cab files into any directory. Allow the Active X to download on its own.
    Tuesday, August 02, 2011 3:43 PM
  • Hi All,

    I am facing same problem "Unable to load client print control".

    I created a report in SSRS 2005 and deployed to Report Server. Ran report from Report Server and there we have Print Symbol. I tried to print report by Clicking on the Print Symbol. It was throwing Error "Unable to load client print control".

    I have gone through these thread but too many solutions are available. Please tell me best solution.  


    Thanks Shiven:) If Answer is Helpful, Please Vote
    Friday, October 21, 2011 9:42 AM
  • We are experiencing the same error. Our environment is as follow Sql and RS server Win 2003 64 bit with Sql 2005 sp3 Client side Win 2008R2 if we use a x 86 browser we are able to print RS reports When using the 64bit browsers we get the "Unable to load client print control" error. We have the "Microsoft Report Viewer 2008 SP1 " installed on the client side. Would appreciate if anybody are able to help
    Monday, January 16, 2012 11:06 AM
  • I am having the same issue as the previous response.  We went through the "killbit" issue early last year, and everything has been working fine, but as far as I know, all users have been using the x86 browser to date.  We've recently added some new clients running the x64 browser, and we're getting the "Unable to load client print control" behavior even after the ActiveX install.    Switching to the x86 browser on the same machine prints fine, but is hardly the ideal "solution" to pass to my client.

    I'd love to know whether this can be confirmed to be related to the same killbit issue or something different?   Or I'd love to hear from anyone that has an SSRS printing solution that *does* work on 64-bit I.E., to prove that it can be done.

    • Proposed as answer by Walter de Jong Wednesday, February 08, 2012 10:42 PM
    • Unproposed as answer by Walter de Jong Wednesday, February 08, 2012 10:42 PM
    Monday, January 23, 2012 4:31 PM
  • We avoid using the client control (and therefore the ActiveX install problem) by using an existing application on the client to display the report:

    E.g. our link to the report specifies using Word, Excel or PDF as appropriate

    we include "rs:Format=Word" in the link e.g. 

    http://servername/ReportServer/Pages/ReportViewer.aspx?%2fLevel1%2fReportName&rs%3aCommand=Render&rs:Format=Word&Parameter=PValue

    Wednesday, February 08, 2012 10:46 PM
  • Hi All,

    I have the Same issue and when I followed below steps it is working fine for my System but How to fix on server that no one should have this issue?

    "The user gets a dialog stating “Unable to load client print control” when clicking the print button on a Reporting Services 2005 report.

    There much written about this and what Microsoft update broke this so I won’t repeat it here. (Google – reporting services “Unable to load client print control”)

    The bottom line is that there’s an update that added a “kill-bit” associated to the ActiveX printing control used by Reporting Services. There’s an update to Reporting Services that supposedly fixes thishttp://www.microsoft.com/downloads/details.aspx?FamilyID=82833f27-081d-4b72-83ef-2836360a904d&DisplayLang=en

    OR you can uninstall these 2 updates KB956803 & KB956391

    OR you can just delete the registry entry causing the problem
    Copy the red text below into a file with a REG file extension and double-click it

    Windows Registry Editor Version 5.00

    [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{FA91DF8D-53AB-455D-AB20-F2F023E498D3}]

    Or Type regedit in Run and then follow the above the path and delete the registry key.

    http://vettekerry.wordpress.com/2009/05/04/unable-to-load-client-print-control-in-reporting-services-2005/

    "

    This link Will Give you evrything:

    http://blogs.msdn.com/b/mariae/archive/2010/04/13/error-unable-to-load-client-print-control-when-printing-reports-in-reporting-services-summary-of-all-possible-causes-at-april-2010.aspx

    Error “Unable to load client print control” when printing reports in Reporting Services (summary of possible causes and solutions)

    RATE THIS
    13 Apr 2010 4:12 AM 

    Due to the great confusion I perceive about this error and its possible causes and solutions, I decided to remove my 3 old posts that talked about this error and create a single and more complete posts that I hope helps you resolve all the possible causes of this error when trying to print reports in Reporting Services. 

    “Unable to load client print control”

    POSSIBLE CAUSES AND PROPOSED SOLUTIONS:

    There could be 2 possible causes for this issue, very differnt from each other:

    1. This error could be caused by a known update to the RSClientPrint control  (MS09-062): http://support.microsoft.com/kb/971023

    There are some fixes already built for this (1. To fix direct accesses to Report Manager 2. To fix applications that access Report Manager like CRM in your case). See bellow:

    1. To fix accesses to Report Manager you should install the following in the Report Server machine:

    Service Pack 3 de Microsoft SQL Server 2005

    http://www.microsoft.com/downloads/details.aspx?displaylang=es&FamilyID=ae7387c3-348c-4faa-8ae5-949fdfbe59c4

    and

    Cumulative update package 8 for SQL Server 2005 Service Pack 3

    http://support.microsoft.com/kb/978915

    2. To fix accesses to the Reporting Services from an application (like CRM, SharePoint or a web application) you would need to install the fixes bellow. They will be different depending on the version of the Report Viewer control:

    To check the version of the ReportViewer control.

    1. Open a report for viewing on a client machine 2. Then right click on the report and select “View Source”.

    Locate the line that looks like this: <script src="http://blogs.msdn.com/TestRSClientPrintReportViewer/Reserved.ReportViewerWebControl.axd?OpType=Resource&amp;Version=X.Y.ZZZZ

    a) If the control type is “Reserved.ReportViewerWebPart.axd” then this is an issue with SharePoint.

    The “Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies” has been updated to work with the new rsclientprint.dll.

    Download center link: http://www.microsoft.com/downloads/details.aspx?FamilyID=1e53f882-0c16-4847-b331-132274ae8c84&displaylang=en

    b) If the control type is “Reserved.ReportViewerWebControl.axd” we should check the following:

    We have 2 different major versions here: 8.00.50727 and 9.00.XXXX. If you see version 8.00.50727 this means you are browsing reports from within CRM or using the ReportViewer control in a custom 2005 web application. If you see version 8.00.50727 and the version is earlier than 8.00.50727.1843 then you should install Report Viewer Redistributable 2005 Service Pack 1 on the ReportServer or on the CRM server or machine where the web application is running:

    Microsoft Report Viewer Redistributable 2005 SP1 (Full Installation)

    http://www.microsoft.com/downloads/details.aspx?familyid=E7D661BA-DC95-4EB3-8916-3E31340DDC2C&displaylang=en

    and

    Report Viewer Redistributable 2005 Service Pack 1 GDIPLUS.DLL Security Update

    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0dfaf300-2b53-4678-a779-0d805ddfe538

    c) If you see version 9.00.XXXX or 9.0.XXXX then you are browsing through Report Manager, Report Server or perhaps a custom web application built with VS 2008. Then you should install the below on the report server and in the machine where the web application is running:

    Microsoft Report Viewer 2008 SP1 Redistributable http://www.microsoft.com/downloads/details.aspx?FamilyID=bb196d5d-76c2-4a0e-9458-267d22b6aac6&DisplayLang=en

    And

    Report Viewer Redistributable 2008 Service Pack 1 GDIPLUS.DLL Security Update

    http://www.microsoft.com/downloads/details.aspx?familyid=6aaa74bd-a46e-4478-b4e1-2063d18d2d42&displaylang=en

    After having updated the ReportViewer control you must issue an iisreset command so that the updated controls will take effect.

    2. Or it could be a permissions issue:

    When trying to print reports from Reporting Services, the RSClientPrinty control needs to be downloaded and installed to the client machines. This is done automatically the first time a user tries to print a report and the users need to be administrators or Power Users in order to be able to download the control though the web.

    Users that are not administrators nor Power Users don’t have permissions to deploy of the RsClientPrint control to IE from the server (not allowed installing ActiveX components)

    This happens the first time you run a report or after installing some cumulative updates or service packs that modifies this control and needs to be redeployed. Each time the client clicks on the print button; there is a round trip to the server to check if the client has the latest version.

    The following links explains that you need administrator permissions in order to download the print control to download it from the server:

    http://msdn.microsoft.com/en-us/library/ms159190(SQL.90).aspx

    2 POSSIBLE ALTERNATIVES:

    Deploy the control manually:

    If the users weren’t administrators or power users, the issue could be resolved by deploying the files manually:

    c:\print\RSClientPrint.dll

    c:\print\rsclientprint.inf

    c:\print\RsClientPrint_1028.rl

    c:\print\RsClientPrint_1031.rl

    c:\print\RsClientPrint_1033.rl

    c:\print\RsClientPrint_1036.rl

    c:\print\RsClientPrint_1040.rl

    c:\print\RsClientPrint_1041.rl

    c:\print\RsClientPrint_1042.rl

    c:\print\RsClientPrint_2052.rl

    c:\print\RsClientPrint_3082.rl

    Or creating a script to install the control using “Run As”

    “Run As” is a tool that allows running programs as a different user than the currently logged-on user. It is described in the article:

     

    How to enable and use the "Run As" command when running programs in Windows

    http://support.microsoft.com/?id=294676

    Steps to create the script would be:

    1.  On a Domain Controller, create a share with the appropriate rights for a "simple user" 2.  On this share create a file called runas.vbs with the following code:

    ' 'RunAs Helper 'Syntax: runas.vbs <username> <command> ' set args=wscript.arguments username = args(0) ' Enter the password in the variable pass pass = "administrator password" 'Get the command arguments for i=1 to args.count - 1 command = command & args.item(i) & " " Next set shell=wscript.createobject("Wscript.shell") 'Run runas.exe shell.run "runas.exe /user:" & username & " """ & command & """",2,FALSE 'Wait for runas.exe to load, this time could be shorter, but is set to 1000 'to be safe wscript.sleep(1000) 'Send the password and hit enter shell.sendkeys pass & "{ENTER}" wscript.sleep(1000)

    3. Extract the dll and inf files from your ActiveX on the share. 4. Download the Windows Script Encoder, available on

    http://www.microsoft.com/downloads/details.aspx?FamilyId=E7877F67-C447-4873-B1B0-21F0626A6329&displaylang=en

    and encrypt the original vbs file: original_vbs_file.vbs vbs_encrypted_file.vbe

    The script encoder is a command-line tool that allows a scriptwriter to protect the contents of a script from unauthorized copies or modifications while ( at the same time ) allowing the script to run.

           5- Create a logonscript with the following instructions:

    net use z: \\server\share <file://\\server\share> 'Map the share to a local drive.

    The files need to be local so as to be installed..

    z:\vbs_encrypted_file.vbe domain\admin rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 z:\rapport.inf z:\vbs_encrypted_file.vbe domain\admin rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 z:\vbs.inf net use z: /d 'Delete the mapping

     


    Thanks Shiven:) If Answer is Helpful, Please Vote




    Wednesday, September 11, 2013 4:45 AM