Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Reporting Services Charts are sized incorrectly or cropped

Reporting Services Charts are sized incorrectly or cropped

Symptoms

When viewing reports using a browser or the HTML renderer that contain a chart, the chart may appear distorted, zoomed or cropped from the expected output. This can occur if Microsoft SQL Server Reporting Services is running on a computer that is running Windows Vista or Windows Server 2008 or a later version of the Windows Operating System.

↑ Back to the top

Cause

This issue occurs when on the computer that is hosting Reporting Services, the default dots per inch (DPI) display setting is set to a value other than 96 DPI. When you use Custom DPI setting on your system  to configure your font DPI to a custom size and then take one of the following actions, some of the old custom DPI settings remain on the system and that causes the images used in the chart to be displayed with the wrong DPI value.:
  • You enable "Windows XP style DPI scaling" from the "Custom DPI Setting" window
    Or
  • You install a different graphics driver or an adapter on the server that does not support custom DPI font settings.Under these conditions, some of the old custom DPI settings remain on the system and that causes the images used in the chart to be created with the wrong DPI value.
Under these conditions, some of the old custom DPI settings remain on the system and that causes the images used in the chart to be created with the wrong DPI value.

↑ Back to the top

Resolution

To resolve this issue use the following procedure on the computer where Microsoft SQL Server Reporting Services is installed:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

Step 1: Find the current custom DPI value

If you use Windows Server 2008 or Windows Vista:
  1. Right-click the desktop, and then click Personalize.
  2. In the Personalization dialog box, click Adjust font size (DPI).

    If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.
  3. In the DPI Scaling dialog box, note the selected DPI value.
If you use Windows Server 2008 R2 or Windows 7:
  1. Navigate to the Display item in Control Panel.
  2. In the Display screen, click Set Custom text size (DPI). The Custom DPI Setting dialog box appears, as shown in the following screen shot
  3. In the CustomDPI Setting dialog box, note the selected DPI value. (For example the value may be: 9 point Segoe UI at 144 pixels per inch )
Note: In Windows 7 environment, you can also get to the Display options by right-clicking on Personalize option on your desktop.4. Open "Registry Editor".

Step 2: Check the value of each of the following registry keys and ensure that it matches the value you noted in Step 1 of this procedure. If it is different, update the value accordingly:

  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Hardware Profiles\Current\Software\Fonts\LogPixels
  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Hardware Profiles\####\Software\Fonts\LogPixels
  • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\FontDPI\LogPixels
Step 3: Reboot the server.

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2588400
Revision : 1
Created on : 1/7/2017
Published on : 3/26/2012
Exists online : False
Views : 280