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

Post a Comment

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.