Bugfix: Something went wrong

Update 2021/2/10: Microsoft stopped creating images for Docker in the summer of 2020. We now publish artifacts, which can be used to spin up containers and BcContainerHelper has replaced NavContainerHelper. This blog post reflects the old way of using NAV/BC on Docker and references NavContainerHelper, which is outdated.

I have had a few partners reporting a strange bug when using the Web Client in Business Central spring release. Running tests, applying configuration packages or running other long running tasks in the Web Client sometimes would result in an error stating: Something went wrong.


Looking in the event log you will see an error stating something like:

Message (NavNSConcurrencyException): RootException: NavNSConcurrencyException
An internal error has occurred. Multiple concurrent calls have been issued to the server from this client.

The cause

The reason for this bug is, that the Web Client is trying to add something to the event log and the right event log has not been created.

The problem exists in NAV 2018 and Business Central containers. I haven’t heard about it before the spring release containers.

The fix

This has been fixed in the Generic NAV / Business Central image version and all Docker images created as of today will include this fix.

The workaround

If you are running into this problem with an existing container image, you have two options:

1. Update your NavContainerHelper to or later, then NavContainerHelper will automatically inject an additional setup script (if the docker image is or lower), which will create the necessary event logs.

2. If you are using Docker without NavContainerHelper, you can override the AdditionalSetup.ps1 script with the same script as NavContainerHelper is using:

Write-Host "Registering event sources"
"MicrosoftDynamicsNAVClientWebClient","MicrosoftDynamicsNAVClientClientService" | % {
    if (-not [System.Diagnostics.EventLog]::SourceExists($_)) {
        $frameworkDir =  (Get-Item "HKLM:\SOFTWARE\Microsoft\.NETFramework").GetValue("InstallRoot")
        New-EventLog -LogName Application -Source $_ -MessageResourceFile (get-item (Join-Path $frameworkDir "*\EventLogMessages.dll")).FullName

This script will also work with new images, it will check whether the event log has been created before creating it.


Freddy Kristiansen
Technical Evangelist

3 thoughts on “Bugfix: Something went wrong

  1. Could it be the same reason/solution for NAV 2017 / Windows Client / NST? We are getting the same error “An internal error has occurred. Multiple concurrent calls have been issued to the server from this client.” in Windows Client, when a user posts and prints a Transfer Order. The custom report uses .Net. In most of the cases (>95%) it works correct, but sometime that error appears. When a user tries again to print the same report later (directly from Transfer Shipment Header), then it works without that error.


  2. Hello

    Am Facing the below Error while trying to use the designer and drag and drop fields

    Error Message : “Something Went Wrong and close the instance ”

    I installed the nav container helper but still the error exists , any ideas ?




    • This blog post was from April 2019 and the bug was related to some specific version back then on docker. Whatever issue you are seeing now, it is probably not this.
      There could be a million reasons for an error like this. If the issue is related to docker you could try to post an issue on http://www.github.com/microsoft/navcontainerhelper/issues – but please specify the script used to create the container, including the full output of that and what you are doing to get the error (follow the issue template)


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s