Skip to main content

Something went wrong. An Error occurred - Error Resolution


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.


  • Microsoft Dynamics Business Central - On-Premise / NAV 2018
  • Understanding of Business Central Authentication 

Books & References:


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 Instance - Ports and Service Account - Business Central Administration

PowerShell Command: 
   -ManagementServicesPort <ServicePort>
   [-ClientServicesPort <ServicePort>]
   [-SOAPServicesPort <ServicePort>]
   [-ODataServicesPort <ServicePort>]
   [-DeveloperServicesPort <ServicePort>]
   [-SnapshotDebuggerServicesPort <ServicePort>]
   [-DatabaseServer <DatabaseServer>]
   [-DatabaseInstance <DatabaseInstance>]
   [-DatabaseName <DatabaseName>]
   [-DatabaseCredentials <PSCredential>]
   [-ClientServicesCredentialType <String>]
   [-ServicesCertificateThumbprint <ClientServicesCertificateThumbprint>]
   [-ServiceAccount <ServiceAccount>]
   [-ServiceAccountCredential <PSCredential>]
   [-ServerInstance] <String>

2. Creation of NAVWebServerInstance:
You will need to run the New- NAVWebServerInstance Powershell command to create WebServer Instance.

Powershell Command: New-NAVWebServerInstance -Server localhost -ServerInstance UAT -WebServerInstance UAT

At this point, both your Server Instance and Web Server Instances are created. These instances are generally created with default configurations provided in the Business Central installation.
Also, if you call the URL, you will get the following error.

3. Update the Web Client Base URL, Port No. in NAVServerInstance:
You will see that the Web Client Base URL is the default one irrespective of your Web Server Instance 
Notice the default Web Client Base URL-
Change the Default Web Client Base URL, ODATA Base URL, and SOAP Base URL  

You will need to set up as 
http or https://<Hostname>/<WebServerInstanceName>/Webclient and port number respectively as per your original Server Instance Setup

4. Update the NavApp Setting JSON file:
You will also observe that the Client Service Port No., Host is copied from the default Webserver Instance configuration.
WebServer Configuration located at C:\inetpub\wwwroot\<WebServer Instance Name>\navsettings.json

Change the ClientServicesPort, ManagementServicesPort, ServerInstance, ClientServicesCredentialType as highlighted

5. Restart NAVServerInstance and NAVWebServerInstance:
Restart the NAVServerInstance through Business Central Administration or Powershell.
Restart the Web Server Instance by restarting IIS Service.
Now, Business Central will work as expected.


I hope this solution helps you or guides you to check the configurations correctly.
If case of any issue feel free to drop a comment or email me at

Thanks and Cheers!!


Popular posts from this blog

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: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation 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 mi

How to update your Business Central to Latest CU

Introduction:  There are times when Microsoft releases the latest major version upgrade for Business Central Upgrade and you face many issues with it. As soon as the bugs are reported to Microsoft, they start to fix them and ask you to upgrade to a certain Cumulative Update. In this blog, I will be sharing my experience with Business Central v21 CU0 upgrade to Business Central v21 CU2. Pre-requisites:  Business Central DVD for Latest CU Basic Understanding of Business Central CU Updates Books & References:  List of Update Packages How to Update CU version Demonstration:  1. Check the current state of BC: As part of knowing the current state of your Business Central environment, I'm assuming that your Business Central Environment will have some data in the standard Base App also there will be customization with extended tables and newly created tables. Customization - TableExtension on Customer Table  Customization - Custom Table created Make a note of the data that is present i