FIX: Barcode font is displayed incorrectly in a report created by using a Report Viewer 2010 control when you export the report to PDF format


Consider the following scenario:
  • You create a report by using a Microsoft Report Viewer 2010 control in Microsoft Visual Studio 2010. 
  • You use the barcode font 'Code 128' in the report, and the report is displayed correctly.
  • You export the report to PDF format.
In this scenario, the barcode is displayed incorrectly.


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must have Microsoft Visual Studio 2010 Services Pack 1 (SP1) installed.

Restart requirement

You do not have to restart the computer after you install the hotfix if the affected files are not being used at the time of installation. We recommend that you close all Visual Studio 2010-related components before you install the hotfix.
File information


To work around this issue, use Microsoft Visual Studio 2012 instead of Visual Studio 2010.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Article ID: 2883844 - Last Review: Nov 28, 2013 - Revision: 1

Microsoft Visual Studio 2010 Service Pack 1, Microsoft Visual Studio 2010 Premium, Microsoft Visual Studio 2010 Professional, Microsoft Visual Studio 2010 Ultimate