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!!

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

Installing LS Central - POS on local machine

Introduction: In this blog, I'm attempting to capture the LS Central - POS installation process on Local Machine. This blog has nothing to do LS Central - Server Setup for POS. LS Retail / LS Central - On Premise POS Pre- requisites : LS Central Installed on Server SSL Setup on LS Server (https://www.olisterr.tech/2020/03/how-to-setup-navuserpassword-with-ssl.html) LS - POS Installer Business Central - On Premise Installer Demonstration: Once your LS Retail / LS Central POS is setup on the main server. Just prior to Go-Live, you will actually have to install this POS on multiple systems and connect these POS to the main server with LS Retail / LS Central. 0.Preparation: Prior to actually installing Business Central On-Premise Windows Client, you need to make sure that you're able to ping the target with the correct Port number. For this I made use of PS-Ping tool.  PSPing - IP Address: Port If you're unable to PS-Ping the correct IP with Port number, simply check the Advan...
Post a Comment
Read more