Skip to main content

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

PowerShell Command: 
New-NAVServerInstance
   -ManagementServicesPort <ServicePort>
   [-ClientServicesPort <ServicePort>]
   [-SOAPServicesPort <ServicePort>]
   [-ODataServicesPort <ServicePort>]
   [-DeveloperServicesPort <ServicePort>]
   [-SnapshotDebuggerServicesPort <ServicePort>]
   [-DatabaseServer <DatabaseServer>]
   [-DatabaseInstance <DatabaseInstance>]
   [-DatabaseName <DatabaseName>]
   [-Multitenant]
   [-DatabaseCredentials <PSCredential>]
   [-ClientServicesCredentialType <String>]
   [-ServicesCertificateThumbprint <ClientServicesCertificateThumbprint>]
   [-ServiceAccount <ServiceAccount>]
   [-ServiceAccountCredential <PSCredential>]
   [-ServerInstance] <String>
   [-Force]
   [-WhatIf]
   [-Confirm]
   [<CommonParameters>]


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 
Name.
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.


Conclusion:

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 olisterr@outlook.com

Thanks and Cheers!!

Comments

Popular posts from this blog

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

How to Upgrade Data from Microsoft Dynamics NAV to Microsoft Dynamics Business Central On Premise - Part 2

 Introduction: Now that the first step of the problem preprocessing of the NAV Database to make it ready to be migrated to BC is done(refer Part 1 ), we can now proceed further with connecting the database in Business Central On-Premise. Pre- requisites : Microsoft Dynamics 365 Business Central Microsoft Dynamics for NAV Microsoft SQL Server Management Studio (SSMS) Powershell ISE Understand NAV to BC Upgrade Considerations -  Click here Understand Upgrade Path -  Click here Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-considerations#online https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-paths https://www.sauravdhyani.com/2018/10/msdyn365bc-data-upgrade-to-microsoft.html https://olisterr.blogspot.com/2022/03/how-to-upgrade-data-from-microsoft.html https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-permissions Demonstration: 1. Install Business