ReportViewer: Export to Excel works on IDE, but not on server due to font issue RRS feed

  • Question

  • Using VS 2005 (VB) to create a web application, I am able to export to Excel with ReportViewer via the IDE, but an exception is raised when performing the same action on the web server.  The exception occurs when the "Export" link on the ReportViewer control is clicked.
    An Exception was generated at 03:59:50 PM on 06 November 2008.
    System.ArgumentException: Font '?' cannot be found. at System.Drawing.FontFamily.GetGdipGenericSansSerif() at System.Drawing.FontFamily.CreateFontFamily(String name, FontCollection fontCollection) at System.Drawing.FontFamily..ctor(String name, Boolean createDefaultOnFail) at System.Drawing.Font..ctor(String familyName, Single emSize) at Microsoft.ReportingServices.Rendering.BIFFUtility.Font.GetData() at Microsoft.ReportingServices.Rendering.BIFFUtility.WorkBook..cctor()

    Looking at other postings on this issue, we reviewed the font folder permissions, and allowed everyone full control, but this didn't help.
    Also the fonts looked ok in WordPad on the server. 
    We are able to export to PDF successfully on the server. 
    The proper ReportViewer files are present in the General Assembly Cache on the server.
    The same error occurs with the RDLC file containing only one textbox with a static string in Arial font.

    Appreciate any help on this.
    Thursday, November 6, 2008 6:03 PM

All replies

  • Hello,

    It looks like someone else had a similar problem (at least based on the exception you are both seeing), and they were able to resolve it.  Here is the thread:

    I know you mentioned that you already adjusted the permissions on your fonts, but perhaps following the same steps as this other user may help.

    Best regards,
    SQL Server Reporting Services
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, November 7, 2008 4:14 PM
  • Thanks for your help.  The problem actually seemed to have disappeared on its own, after several days of trying different font folder permission settings, and IIS & server restarts failed to make any difference.  I read on the web that the exact same issue and resolution happened to someone else. 
    Tuesday, December 2, 2008 6:44 PM