About This Blog

.net & SQL Samples, programming tips and tricks, performance tips, guidelines, and best practices

Tuesday, 29 November 2011

Workarounds for SSRS 2008 Font Rendering Issue in ReportViewer 10.0


Problem
A report developed using SSRS 2008 either through Visual Studio 2010 or BIDS 2008 does not renders properly when viewed in the Report Viewer 10.0 via Remote Desktop or any 3rd party applications using Terminal Services in the background.
Remote Rendering



Local Rendering



Workarounds
  1. Change the Screen Resolution to 1024 X 768 or any 4:3 aspect ratio for both the Remote machine as well as the local machine.
  2. Export the report as PDF and then take the print outs if required.
  3. If the above two solutions does not work for you, unfortunately you will have to look back to SSRS 2005.
Hope, this saves you some time of searching.
Posted by at
Labels:

14 comments:

  1. Anonymous17 June 2012 at 21:47

    Thanks for your instructions. However this doesnt seem to solve my issue. I tried in a 1024 resolution.

    ReplyDelete
    Replies
    1. vinay pugalia17 June 2012 at 23:13

      Hello,
      Can you please share some details of your environment and setup. It might help in resolving the issue.

      Delete
  2. vinay pugalia1 March 2013 at 20:57

    Hello Readers,
    Today I have found the fix for the above stated issue and "Mr.Jing Tong" Reporting Services developer, Microsoft has shared the solution for this as under - AS IS -

    Thank you for reporting this issue. This is a known problem and it took a long time for the Reporting Services and Dynamics NAV developers to investigate and dissect the root cause to a Windows Remote Desktop Protocol issue.

    There are 2 solutions available:
    1. Upgrade the VB2010 host machine to Windows 8 or Windows Server 2012.
    2. Install the Windows Remote Desktop hotfix from http://support.microsoft.com/kb/2768741 for Windows 7 or Windows Server 2008R2 OS.

    Thank you,
    Jing Tong
    Reporting Services developer, Microsoft

    Hope, this helps!

    ReplyDelete
    Replies
    1. Anonymous20 January 2014 at 08:43

      Thanks, it works with hotfix...

      Delete
  3. lfmdk30 June 2013 at 22:51

    Thank you very much, it have saved me a lot of time. and the suggested workaround works, I will try the update later.

    ReplyDelete
  4. ಅರುಣ್ ಜಾವಗಲ್25 July 2013 at 03:26

    Thank you.... This workaround worked!!

    ReplyDelete
  5. Unknown16 December 2013 at 13:39

    Hi, I tried all the workarounds and the hotfix but nothing seems to be working. We use Windows Server 2008R2. I am scratching my head with this issue for quite sometime now. Any help will be very much appreciated!

    ReplyDelete
  6. vinay pugalia16 December 2013 at 20:38

    Ramkumar,

    These are are only known workarounds AFAIK. They work in some environment & doesn't in other.

    However, try upgrading your reports to Report Viewer 2012 - http://www.microsoft.com/en-in/download/details.aspx?id=35747

    I have not tested it yet, but this issue might have been solved in this version.

    Please do leave back a comment with your findings.

    Thanks!

    ReplyDelete
  7. Anonymous11 March 2014 at 01:56

    Thanks
    It Works

    ReplyDelete
  8. Alex Ng17 February 2016 at 03:12

    Thanks for your article but sadly this does not work for me. I am running my application on Windows 7 accessed through VirtualBox. The screen resolution is 1600x900. There are no problem if it is run at 1024x768.

    I noted that only Rdpdd.dll at Windows\System32\drivers was updated. The Rdpwd.sys still had a file date in 2010. Am I installing the hotfix incorrectly?

    Thanks!

    - Alex

    ReplyDelete
  9. Unknown27 July 2016 at 12:39

    This worked for me: https://support.microsoft.com/en-us/kb/2768741

    ReplyDelete
  10. Unknown10 August 2017 at 16:34

    worked for me too

    ReplyDelete
  11. Anonymous6 December 2019 at 08:16

    Thank you! I had to keep an old project alive long enough for the rewrite. The hotfix saved the day!

    ReplyDelete
  12. Anjali13 October 2020 at 17:34

    Yes this resolves the issue for win7 machines

    ReplyDelete

Subscribe to: Post Comments (Atom)