This is usually caused by the workstation not having enough permissions to download the RSClient print control from the SQL server. Essentially it’s just a set of files that get downloaded and registered on the workstation. Make sure someone can login to the workstation as an admin and print a facesheet or report. They should get a prompt that will ask them to down the SQL print control from the server like in the screenshots below. Once it has been installed as the windows admin user, it should load properly for a standard user. One way to view the print control is by navigating to the IE settings > Programs tab > Manage add-ons button > you should see an add-on called ‘RSClient Print Class’. The version may be different depending on the version of the RSClient print control on the SQL server.

There have been cases where the add-on appears in this list but it still needs to be downloaded. To force it to download, you can navigate to this path "C:\Windows\Downloaded Program Files\", run a search for rsclient which should return 13 files, and delete the 13 files. Make sure you have IE closed when doing this. Then when you try to print a facesheet or report again, you will get a prompt to download the rsclient print control again. 

This is the add-on that gets downloaded from the server:

These are a few of the prompts they might see when it tries to download the print control as an admin:

Once that is complete, users will be able to print facesheets and reports.

Please note that there are different versions of the RSclientprint controls that are linked to your version of SQL server and the SQL service pack that you have installed. The version of RsClientPrint you get with SQL 2008 R2 with SP2 is 10.50.4000, while the RTM version is 10.50.1600. The RTM version is not compatible with IE10 or higher and you will need to have the SQL service pack updated. To see what version of SQL server you have, run Select @@version as a query in SSMS.