A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
The clue is the single OTF file. The SSRS PDF renderer only embeds a font when it's TrueType, the font allows embedding, and it's installed on the report server. An .otf file often fails the first check, so the font isn't embedded. Acrobat then looks for "XYZ,Bold" on the viewing PC, can't find it, and shows that warning. The ",Bold" part appears because there's no separate bold font file, so the bold text has nothing real to map to.
- Ask the customer for the TrueType (.ttf) version of the font, including the Bold weight (and Italic if the reports use it).
- Confirm the font licence allows embedding. If the font is marked no-embedding, SSRS won't embed it whatever the format.
- Install all the .ttf files for all users on the report server.
- Restart the SQL Server Reporting Services service so it picks up the new fonts.
- Export a report to PDF again. In Acrobat, open File > Properties > Fonts and check that XYZ and XYZ Bold show as "Embedded Subset".
If a TrueType version isn't available, the other option is to remove bold formatting from text using that font.
Do the fonts list in Acrobat show XYZ as embedded at all right now?
If the PDF opens cleanly after this, please consider accepting it as the answer. If the font still isn't embedded with the .ttf files, let me know and I'll be happy to keep helping.
Reference: