Cannot install the Client Print control

  • This is something I've encountered before at my previous job, but all of my notes on how to resolve it are - well back there.

    One of our applications here is on a Windows 2008 R2 Server, running in SQL Server 2008 R2. It generates reports fine. When the user (any user, including myself) tried to print the SSRS report using the print button we first the UAC asking if we want to install the print control. Then we get the dreaded, "Unable to load client print control" error message.

    I've searched the Internet and these forums, but most of what I've found is older - dealing with SSRS 2005, or Window Server 2003. I'm thinking that this might have changed with SQL Server 2008 R2 (and SSRS 2008 R2) and Windows Server 2008 R2. So, are things different? What's the procedure now to resolve this?

    Kindest Regards, Rod Connect with me on LinkedIn.

  • Not sure why you would want to run a report from a server instead of a client. Are you doing this on IE or another type of browser? If it is IE have you tried with Enhanced Security Configuration disabled?

    Joie Andrew
    "Since 1982"

  • Well, actually in this case I am trying to run it from the client. I believe the reports are all .RDLC files, so they'll run "locally".

    We are trying to run the reports in IE. I haven't tried disabling Enhanced Security Configuration. I'll give that a try and see what happens.

    Kindest Regards, Rod Connect with me on LinkedIn.

  • Sorry. I misunderstood. I do not think ESC will help you as that is a server feature.

    What happens if you run IE with a local admin account? Can it print then?

    Anything in the client event logs?

    Joie Andrew
    "Since 1982"

  • Joie Andrew (7/8/2015)


    Sorry. I misunderstood. I do not think ESC will help you as that is a server feature.

    What happens if you run IE with a local admin account? Can it print then?

    Anything in the client event logs?

    OK, that actually worked; running IE as administrator. However I realized that's not going to do our users any good as none of them have local administrative privileges.

    Kindest Regards, Rod Connect with me on LinkedIn.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply