Skip to main content

Universal Code Error and Resolution


On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows.
This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license.


  • Understanding of Technical Upgrade in Business Central On-Prem


Root Cause:

The certificate that signs Microsoft Base Application was expired.
Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out.

We first thought could be a license issue as we had fixed that before but this did not solve the issue.


Microsoft identified the issue and posted the following update
The mitigation is to do a technical upgrade to a version that has a change that also fixes this issue.
19.18+ or 20.12+ or 21.6+  or 22+
Only a technical upgrade is required.

This approach is similar to doing a CU upgrade(Technical Upgrade - Installation) refer to know how to upgrade your Business Central to latest CU.

However, you do not need to upgrade the Application.
You can also manually do the upgrade by patching the files as follows


If you are on any older versions of 19,20,21 or 22, we recommend you upgrade to a version which is 19.18+, 20.12+, 21.6+ and 22+


Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Setting up OAuth Authentication for Business Central Web Services / APIs

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr