Getting Crystal to properly embed TT fonts in a PDF

Question

Has anyone run into problems getting Crystal XI to embed fonts when displaying reports via the web (served by RAS) and then exporting to PDF? We have a barcode font that we use in a few reports, and it worked fine via the web viewer and when exporting to PDF. When we moved our reporting server from a 2000 box to a 2003 box, the font is no longer exported. It does display properly in the html viewer, but when you export it to PDF to print, the PDF doesn't contain the font. The True Type font is installed on the new server, with scandalously lenient permissions, and the font is installed on all the client machines. Is there no way to start Crystal in some sort of "debug" mode where it will emit info on what it is doing?

(Edited to specify that it is only when exporting to PDF through a page served by RAS that the font is not embedded)

Answer 1

So far I've come across some info that doesn't help me but might help others with similar symptoms:

One issue that can arise is that Crystal won't embed fonts that have DRM on them. See this utility to remove DRM if need be. Microsoft also has a utility to tell you more than you ever wanted to know about your true type fonts, including their "embeddable" status. Sadly, my fonts are already embeddable so this did not help me.

EDIT: FOUND SOLUTION! The solution here worked for me. The relevant part was this:

On the Windows 2003 PC open Control Panel, and double click on Regional and Language Options. Click on the Language Tab and check on Install Fonts for complex scripts.... Now click on the Advanced tab and in Default user account settings check on apply all settings....

Answer 2

Windows Server 2008 supposedly already has fonts for complex scripts enabled according to the article here.

The option "Advanced tab and in Default user account settings check on apply all settings" setting is similar in Server 2008 but you can select Default User And and / or System accounts.

This solution worked on Server 2003 and we are testing it on Server 2008. Note that on Server 2003 we had to perform a complete system restart in order for the changes to take affect.