Skip to main content

MSDYN365BC - OnPrem Custom Font with Web Client.

Hi Readers,

Yesterday we stuck with an issue for a customer which we recently upgraded to Business Central 13.x on-prem. It took time to find the solution so I thought to share a solution with everyone.

Issue Description - Report using custom Barcode Font does not work with Web client but works with the windows client.


In this article, we will discuss the issue and resolution on same.


Where Font needs to be installed?

  • If a report uses a custom font (like barcode font) then we need to make sure that custom font is installed in Every NAV Server and Web Client Server.
Did It work after Installing Font on Servers?
  • No Report still didn't print barcode even after installing the font on the servers.
What was the cause of the issue?
  • We had no idea what was the cause of the issue. We tried all general stuff like -
    • Restarting Service Tier.
    • Restarting IIS Server.
    • Restarting Servers.
  • With Windows Server 2019, there is a new option while installing fonts.
    • Don't Choose to Install for the font file.
    • Use Install for all users for the font file.

Hope this article help you, with Windows Server 2019 and Custom Font for Business Central on-prem.

Regards,
Saurav Dhyani

Comments

  1. Thank you for sharing this info! I am using Business Central wave2 cu1 (BC150 CU1) with Windows server 2019. The solution for me was installing font for all users as mentioned.

    Thank you Saurav Dhyani!

    ReplyDelete
    Replies
    1. Welcome +Gregor,
      Its great to hear that i was able to help.

      Delete
  2. perfect hint with "Install for all users"

    ReplyDelete
    Replies
    1. It's great to hear that article was able to help you.

      Delete
  3. Thank you very much. You made me look stupid after the whole day of research, but now it finally works!

    ReplyDelete
    Replies
    1. I am sorry you wasted your time but at same time i am happy that i was able to help.

      Delete

Post a Comment

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searching for the error i figured out the issue was due to - Design change in NA

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.