Knowledgebase: FDM
FDM Report Tries to Publish with "Error 212: Couldn't export PDF using font because characters referencing this font could not be represented with the character encoding"
Posted by Priya Doyle on 08 February 2011 03:37 PM

FDM Report Tries to Publish with "Error 212: Couldn't export PDF using font because characters referencing this font could not be represented with the character encoding" 

 Modified 23-APR-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.2.0.0.00 to 11.1.1.0.00 - Release: 9.2 to 11.1
Information in this document applies to any platform.

Symptoms

When trying to publish a report to PDF, the following error is returned:

** Begin FDM Runtime Error Log Entry [2008-07-28-11:08:04] 
------------------------------------------------------------- 
ERROR: 
Code......................................... -2147467259 
Description.................................. ActiveReports PDF export DLL error 
Error 212:Couldn't export PDF using font 'Times New Roman' because characters referencing this font could not be represented with the character encoding 'WinAnsiEncoding.' 
Use: 
MyPDFExportInstance.AcrobatVersion = 2 
MyPDFExportInstance.SemiDelimitedNeverEmbedFonts = "" 
Procedure.................................... clsAppServer.fPublishReport 
Component.................................... upsAppSv 
Version...................................... 931 
Thread....................................... 5588

Cause

Some text in the report is a UNICODE style text that is not supported by the default font.
FDM reports were not written for localization.

Solution

As there are many reports for FDM, it is best to approach this as a one-on-one situation.

You can edit each of the reports that cause an error and change the font to a unicode font.  Such as Arial Unicode.

(0 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments: