Skip to main content

Universal Code Error and Resolution

Introduction:

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.

Pre-requisites: 

  • Understanding of Technical Upgrade in Business Central On-Prem

References:

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.


Resolution:

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 https://www.olisterr.tech/2023/01/how-to-update-your-business-central-to.html 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

Conclusion:

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+


Labels:

Comments

Post a Comment

Let me know your comments below. I'll try my best to answer your comment

Popular posts from this blog

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Ed...
Post a Comment
Read more

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: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant 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...
Post a Comment
Read more

How to Setup NavUserPassword with SSL for Microsoft Dynamics Business Central(NAVISION ERP)

Introduction: In this blog, I'm attempting to setup basic authentication like NavUserPassword for Business Central On-Premise. NavUserPassword is an authentication system, where each user have their own UserID and password which is configured inside Business Central itself. Pre- requisites : Microsoft Dynamics 365 Business Central On-Premise Domain for your VM Understanding of Credential Types in Business Central Demonstration: 1. Setup DNS in Azure VM: Go to your VM inside Azure to configure DNS. Click on Configure Put the URL as you need. 2.  Create a Webserver Instance for Business Central: New-NAVWebServerInstance to create a Web Server Instance Adding Web Server Instance with the name LS 3. Create a Self Signed Certificate or get an SSL from Domain provider: Run the PowerShell script to create a self signed certificate New Self-Signed Certificate New Self-Signed Certificate created After creation/installation of Certificate, righ...
4 comments
Read more