Initialization of new container fails

Business Central/NAV Technical Forum
1

I really love working with Docker containers. Before I usually took 1-2 hours to be able to test out a new version. Now I can get a new version up and running in 5-10 minutes (depending how much it needs to download first).

But recently I have been having some issues. This is what it says is happening.

Starting NAV Service Tier
Using license file ‘c:\run\my\license.flf’
Import License
Microsoft Dynamics 365 Business Central Server is currently not ready to serve requests. Try again later, or contact your system administrator.
at , C:\Run\SetupLicense.ps1: line 29
at , C:\Run\navstart.ps1: line 126
at , C:\Run\start.ps1: line 107
at , : line 1

TimeGenerated : 10/5/2018 12:08:58 PM
EntryType : Warning
Message : Type: Microsoft.Dynamics.Nav.Types.NavServerNotFoundException

The only thing that I have been able to figure out, is that it doesn’t start the BC Server. It fails on loading the license, but because the service isn’t running.

I first had this issue a couple of months ago. Here I were able to “fix” it, by lowering the memory to 4GB. Tried to lower to 3GB, but the same issue.

The thing is that it works with the RTM, but not with the insider builds.

Did anyone see this issue or got a clue what it could be?

2

Hi Erik!

How is your setup?

I have had no problems of such kind. I am currently running a Windows 10 Pro with hyper-V. Within hyper-V I am running a WIndows Server 2016 (two actually - one with GUI and one without).

What I do is that i Start my Windows Server 2016 with GUI and run the following Sandbox.ps1 file:

$Licensefile = “C:\Docker\20180924 - NAVspecialist - NAV2018 - 6197658.flf”
$ImageName = “bcinsider.azurecr.io/bcsandbox:dk”
$ContainerName = “sandbox”
$PlainTextPw = “Passw0rd”
$Credential = New-Object -TypeName PSCredential -ArgumentList $env:USERNAME,(ConvertTo-SecureString -String $PlainTextPw -AsPlainText -Force)
New-NavContainer -containerName $ContainerName -memoryLimit “3g” -accept_eula -accept_outdated -auth NavUserPassword -Credential $Credential -imageName $ImageName -licenseFile $Licensefile -includeCSide -shortcuts Desktop -additionalParameters @("–network=tlan","–ip 172.21.31.11") -verbose

And I have not yet have had any problems (the last two months)

My docker-version says:

docker version
Client:
Version: 17.06.2-ee-16
API version: 1.30
Go version: go1.8.7
Git commit: 9ef4f0a
Built: Thu Jul 26 16:43:19 2018
OS/Arch: windows/amd64

Server:
Engine:
Version: 17.06.2-ee-16
API version: 1.30 (minimum version 1.24)
Go version: go1.8.7
Git commit: 9ef4f0a
Built: Thu Jul 26 16:52:17 2018
OS/Arch: windows/amd64
Experimental: false

Docker was installed by using powershell:

Install-WindowsFeature containers
Restart-Computer -Force

Install-Module -Name DockerMsftProvider -Repository PSGallery -Force
Install-Package -Name docker -ProviderName DockerMsftProvider
Restart-Computer -Force

3

The RTM image works fine. Try with the insider builds:

bcinsider.azurecr.io/bcsandbox-master

4

Also a problem here:

Import License
Microsoft Dynamics 365 Business Central Server is currently not ready to serve requests. Try again later, or contact your system administrator.
at , C:\Run\SetupLicense.ps1: line 29
at , C:\Run\navstart.ps1: line 126
at , C:\Run\start.ps1: line 107
at , : line 1

TimeGenerated : 10/8/2018 11:21:15 AM
EntryType : Warning
Message : Server instance: NAV
Tenant:
The service could not remove service principal names because
the service account could not be found in Active Directory.
Account: NT AUTHORITY\SYSTEM
Service principal names:
http/insider:7048
http/insider:7048
To avoid this warning, make sure the server account is
provisioned correctly (see
go.microsoft.com/…/ ).

TimeGenerated : 10/8/2018 11:21:15 AM
EntryType : Warning
Message : Server instance: NAV
Tenant:
The service could not remove service principal names because
the service account could not be found in Active Directory.
Account: NT AUTHORITY\SYSTEM
Service principal names:
http/insider:7047
http/insider:7047

I think the image needs an investigation by FreddyK - I think its a a (execution) permission issue.

5

What I noticed, was that it creates a certificate, even if UseSSL = true…

But yes, this may be something Freddy should take a look at.

6

I think the issue is SQL Permission related… that is at least what “DOCKER logs insider” says…

7

Well Freddy confirmed the issue. The insider master is currently broken.

8

And issue was fixed in the next build available from Microsoft. That’s the problem using the daily master builds. They are really alpha builds. [emoticon:c4563cd7d5574777a71c318021cbbcc8]