Skip to content

fix: address sql assembly conflict when creating clean database #4110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
warlof wants to merge 4 commits into
base: main
Choose a base branch
from
+16 −1
Open

fix: address sql assembly conflict when creating clean database #4110

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ba53165
fix: address sql assembly conflict when creating clean database
warlof Mar 17, 2026
c18f93f
Merge branch 'main' into fix/issue-4051
warlof Mar 31, 2026
04dfd53
docs: update changelog with new-bccontainer changes
warlof Mar 31, 2026
120aaf0
Merge branch 'main' into fix/issue-4051
warlof Apr 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 15 additions & 1 deletion ContainerHandling/New-NavContainer.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2308,14 +2308,28 @@ if (-not `$restartingInstance) {
Set-NavserverInstance -ServerInstance $serverInstance -stop
Copy-NavDatabase -SourceDatabaseName $databaseName -DestinationDatabaseName "tenant"
Remove-NavDatabase -DatabaseName $databaseName
Write-Host "Exporting Application to $DatabaseName"
Invoke-sqlcmd -serverinstance "$DatabaseServer\$DatabaseInstance" -Database tenant -query 'CREATE USER "NT AUTHORITY\SYSTEM" FOR LOGIN "NT AUTHORITY\SYSTEM";'
}

# mitigate issue with Microsoft.SqlServer.SmoExtended assembly
# Could not load type 'Microsoft.SqlServer.Management.Common.TransferException' (caused by legacy loaded assemblies in upper stack)
Remove-BcContainerSession -ContainerName $containerName

Invoke-ScriptInBCContainer -containerName $containerName -scriptblock {
$customConfigFile = Join-Path (Get-Item "C:\Program Files\Microsoft Dynamics NAV\*\Service").FullName "CustomSettings.config"
[xml]$customConfig = [System.IO.File]::ReadAllText($customConfigFile)
$databaseServer = $customConfig.SelectSingleNode("//appSettings/add[@key='DatabaseServer']").Value
$databaseInstance = $customConfig.SelectSingleNode("//appSettings/add[@key='DatabaseInstance']").Value
$databaseName = $customConfig.SelectSingleNode("//appSettings/add[@key='DatabaseName']").Value

Write-Host "Exporting Application to $DatabaseName"
Export-NAVApplication -DatabaseServer $DatabaseServer -DatabaseInstance $DatabaseInstance -DatabaseName "tenant" -DestinationDatabaseName $databaseName -Force -ServiceAccount 'NT AUTHORITY\SYSTEM' | Out-Null
Write-Host "Removing Application from tenant"
Remove-NAVApplication -DatabaseServer $DatabaseServer -DatabaseInstance $DatabaseInstance -DatabaseName "tenant" -Force | Out-Null
Set-NAVServerConfiguration -ServerInstance $ServerInstance -KeyName "Multitenant" -KeyValue "true" -ApplyTo ConfigFile
Set-NavserverInstance -ServerInstance $serverInstance -start
}

$allowAppDatabaseWrite = ($additionalparameters | Where-Object { $_ -like "*defaultTenantHasAllowAppDatabaseWrite=Y" }) -ne $null
New-BcContainerTenant -containerName $containerName -tenantId default -allowAppDatabaseWrite:$allowAppDatabaseWrite
}
Expand Down