Crystal Reports runtime does not export barcode font to PDF

[robert_willson]

I am using Crystal Reports runtime for .NET ver 13.0.21.2533 on Windows server 2022 Datacenter.  Also using standard Crystal Reports 2016 for Sage.  Using Azalea Code128 True Type font for barcodes in the report.  Barcodes are also installed on the client PC.

The barcodes in the report show up fine on the server and client in the Crystal Report preview.  Exporting this to Word or Excel also preserves the barcode font.  However, when exported to PDF, the barcode font disappears and only text remains.

I have a second server where this problem was fixed, but the solution has been lost.

[DonWilliams · Accepted solution]

First thing you need to do is upgrade to the latest SP 37 from here:

https://help.sap.com/docs/SUPPORT_CONTENT/crystalreports/3354091173.html

SP 21 is quite old and missing a lot of updates and security fixes.

Likely cause is PDF is blocking the embedding into the PDF due to licensing or possibly missing the UFL or the font is not in the correct location.

ProcessMonitor may show what's missing, compare the logs between the 2 PC's.

[robert_willson · Accepted solution]

Updated to SP37 did not fix the issue. The font was added to the standard fonts in control panel, if there is a different location I don't know where it is. How do I access ProcessMonitor? Standard windows event logs don't show anything.

[DonWilliams · Accepted solution]

Did you copy over the Azalea UFL to the Server?

[robert_willson · Accepted solution]

On the old server, there was some kind of Azalea setup program in 2022 which doesn’t exist in the new download from their website, instead it's just the font files which I already have installed. There is a u2lbcode.dll that was used on the old server somewhere, and possibly a UFL as well, but I’m not sure. I'm contacting Azalea to see if they can help.

[DonWilliams · Accepted solution]

Open the report and Preview it, then click on Help... About... and the More Info button.

You will see what dll's are being used. Likely one you are missing is the Azalea UFL dll

You can also ProcessMontior, it too will list the dll's used, you can compare the list on the working PC with the Server and copy over the CR dll's missing.

[robert_willson · Accepted solution]

The file u25azalea.dll is in the win32_x86 directory on both servers. When using the "SAP Crystal Reports 2016 for Sage" program, I am able to export to PDF with barcodes. However, I am using the .NET runtime version, and when that is used I cannot export barcodes to PDF. There are other directories in the SAP BusinessObjects directory, those all have the correct .dll file on both servers.

[DonWilliams · Accepted solution]

Contact Azalea and ask them for the installer. Does the Log file show the fonts are being accessed?

I found this also on their site:

https://www.azaleabarcodes.com/code-128/crystal-reports/

There is a download button...

Open a PDF and select options or properties and the Font tab, it likely says why the font was substituted:

It could be there is a missing License File for code 128, CR won't embed Licensed fonts in PDF's due to licensing permissions.

Azalea's installer likely added that file, look in the font folder for license files, typically they have a .lic extension.

CR install Azalea code39 barcode fonts, do a quick test and see if those exports?

[robert_willson · Accepted solution]

Code39Azalea fonts work. Code128 fonts show a substitution to Ariel in the PDF properties. Cannot find a .lic file in the working server fonts directory, but it could be hidden somewhere else. Azalea support said they stopped using an installer, now only provide the font files. Still working with them. Unfortunately I cannot use Code39 due to my character set

[robert_willson · Accepted solution]

Problem solved. Code128 requires the "Azalea C128Tools" installation package in order to export to PDF on Crystal Reports .NET runtime. This package is only available on request at azaleabarcodes.com