Home› General
ReportBuilder 22.06 now available including Delphi 12.2 support!
New Blog Posts: Merging Reports - Part 1 and Part 2

Exception: CreateFontPackage Error: 1009 when converting to PDF

rbuserrbuser
edited February 2016 in General
Hello,

Recently we go the following exception when converting a report to PDF:

"Exception: CreateFontPackage Error: 1009"

The exception happend in a call to "ppWinEmbedFont.ppCreateFontPackage".
In this method there is a call to "CreateFontPackage" from "FONTSUB.dll"
which gives the code "1009" as function result.

I have done a some research on the net and found out that the error
description is "ERR_NO_GLYPHS" but i was not able to find any usefull
information what would be the cause of this error.

The error happens only on one system, did not happen the days before
and so i am currently investigating what may have changed on that system
(will have to talk to our admins). However our software and the used
report are still the same so the change must be somewhere else on that
computer.

Can you give me a hint what may be the cause of this error?

Thanks in advance,
Ralf

Comments

  • nicociziknicocizik
    edited February 2016
    Hi Ralf,

    CreateFontPackage is a Windows API routine we use to generate valid font
    subset files to embed in PDF files to reduce space. From past
    experience we have found that this routine is very picky about the fonts
    it processes.

    My guess is that a non-standard font is being used inside the report and
    that is causing the "no glyphs found" error. We have tested all
    natively installed fonts included with Windows with this function
    however cannot guarantee that other third party fonts will process
    correctly.

    If the font causing the error must be used, you can turn font subsetting
    off by setting the PDFSettings.EmbedFontOptions.efUseSubset property to
    false (or removing it from the set in code).

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • rbuserrbuser
    edited February 2016
    Am 10.02.2016 um 16:06 schrieb Nico Cizik (Digital Metaphors):



    Hello Nico,

    That was my guess when i saw that error!

    I think i will tell our admins to restore the font directory on that machine
    from a backup (the report and the software did not change since it was working,
    so it has to be something "outside" our software)

    Thanks for clarification!

    Ciao,
    Ralf


    ---
    Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
    https://www.avast.com/antivirus
This discussion has been closed.