SSRS print dialog doesn't open

Allen M 11 Reputation points
2020-08-21T18:40:38.247+00:00

19581-capture.png

We have a number of users saying the print dialog doesn't open when pressing the highlighted button. They all said it followed a recent windows update (quite a number in the first week of August 2020). Users are all IE11.
Some were fixed by unchecking 'do not store encrypted files' in their browser settings but that only fixed a few. Has anyone else experienced this and/or suggestions to trouble shoot?

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
3,061 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. ZoeHui-MSFT 41,491 Reputation points
    2020-08-24T03:16:16.267+00:00

    Hi,

    Could you help check the following situations?

    1.Could the users print the reports by Chrome or Edge.

    2.When they press the print button, it shows no error message, am I right?

    3.Open the reports through the Visual Studio or Report Builder, could them print the reports?

    19793-3333.png
    19802-44.png

    4.Choose "Check for updates" in start menu, uninstall the newest update for a try.

    5.What's your version of SSRS.

    Regards,

    Zoe

    0 comments No comments

  2. Allen M 11 Reputation points
    2020-08-24T12:23:30.757+00:00
    1. That print button doesn't exist in Chrome or Edge.
    2. That is correct.
    3. I am able to print the report.
    4. I will investigate this option.
    5. Microsoft SQL Server Reporting Services Version 11.0.7001.0

  3. Allen M 11 Reputation points
    2020-08-25T12:24:09.023+00:00

    Unfortunately I'm unable to determine which windows update was installed.
    Yes the users can use the save to disk option which is what they've been doing as a workaround.


  4. Debashis Pal 0 Reputation points
    2023-12-04T09:28:50.16+00:00

    For me, it was a consistent issue. The same works in my local (SQL Server 2016) but once published to server (SQL Server 2014), this became an issue. I have upgraded the SQL Server 2014 to 2016 (in server) and this issue is resolved.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.