navcontainerhelper icon indicating copy to clipboard operation
navcontainerhelper copied to clipboard
verified publisher icon microsoft

External Azure Database connectivity to BC container

Open manjunathan-ganesan opened this issue 7 months ago • 8 comments

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!

Describe the issue I'm unable to connect to one of the Azure database from the container dbcentral:sandbox-26.1.33404.34384-us-nodb, which is based on the mcr.microsoft.com/businesscentral:ltsc2022 image.

Scripts used to create container and cause the issue

$containerName = 'bcserver'
$credential = Get-Credential -Message 'Using UserPassword authentication. Please enter credentials for the container.'
$auth = 'UserPassword'
$artifactUrl = Get-BcArtifactUrl -type 'Sandbox' -country 'us' -select 'Latest'
$databaseServer = 'XXXXXXXXXX.windows.net'
$databaseInstance = ''
$databaseName = 'backup_prod'
$databaseUsername = 'XXXXXXX'
$databasePassword = 'XXXXXXXXX'
$databaseSecurePassword = ConvertTo-SecureString -String $databasePassword -AsPlainText -Force
$databaseCredential = New-Object pscredential $databaseUsername, $databaseSecurePassword
New-BcContainer `
    -accept_eula `
    -containerName $containerName `
    -credential $credential `
    -auth $auth `
    -artifactUrl $artifactUrl `
    -imageName 'dbcentral' `
    -databaseServer $databaseServer -databaseInstance $databaseInstance -databaseName $databaseName `
    -databaseCredential $databaseCredential `
    -dns '8.8.8.8' `
    -memoryLimit 8G `
    -updateHosts

Full output of scripts

BcContainerHelper version 6.1.3
WinRM service is not running, will not try to use WinRM sessions
BC.HelperFunctions emits usage statistics telemetry to Microsoft
Running on Windows, PowerShell 5.1.26100.4061
Downloading Platform index to C:\Users\xxxxx\AppData\Local\Temp\bcContainerHelper.platform.json
Downloading us index to C:\Users\xxxx\AppData\Local\Temp\bcContainerHelper.us.json
BcContainerHelper is version 6.1.3
BcContainerHelper is running as administrator
HyperV is Enabled
Host is Microsoft Windows 11 Pro - 10.0.26100.4061
UsePsSession is True
UsePwshForBc24 is True
UseWinRmSession is never
UseSslForWinRmSession is True
Docker Client Version is 28.0.4
Docker Server Version is 28.0.4
Removing Session bcserver
Removing container bcserver
Removing entries from hosts
Removing bcserver from container hosts file
Removing bcserver-* from container hosts file
Removing Desktop shortcuts
Removing C:\ProgramData\BcContainerHelper\Extensions\bcserver
Fetching all docker images
Fetching all docker volumes
ArtifactUrl and ImageName specified
Building image dbcentral:sandbox-26.1.33404.34384-us-nodb based on mcr.microsoft.com/businesscentral:ltsc2022 with https://bcartifacts-exdbf9fwegejdqak
.b02.azurefd.net/sandbox/26.1.33404.34384/us without database
Pulling latest image mcr.microsoft.com/businesscentral:ltsc2022
ltsc2022: Pulling from businesscentral
Digest: sha256:e277669d43b08c8fdff52efcb73e6645bcd0cf4e23cb7466f052dcbb6f39b1fa
Generic Tag: 1.0.2.64
Container OS Version: 10.0.20348.3566 (ltsc2022)
Host OS Version: 10.0.26100.4061 (24H2)
Host OS is 26100 (24H2) or above, recommended isolation mode is hyperv.
Using hyperv isolation
Files in c:\bcartifacts.cache\wt55p4ij.dtr\my:
Copying Platform Artifacts
c:\bcartifacts.cache\sandbox\26.1.33404.34384\platform
Copying ConfigurationPackages
C:\bcartifacts.cache\sandbox\26.1.33404.34384\us\ConfigurationPackages
Copying Extensions
C:\bcartifacts.cache\sandbox\26.1.33404.34384\us\Extensions
Copying Applications.US
C:\bcartifacts.cache\sandbox\26.1.33404.34384\us\Applications.US
c:\bcartifacts.cache\wt55p4ij.dtr
Sending build context to Docker daemon  2.312GB

Step 1/6 : FROM mcr.microsoft.com/businesscentral:ltsc2022
 ---> 0bf4df0fe40f
Step 2/6 : ENV DatabaseServer=localhost DatabaseInstance=SQLEXPRESS DatabaseName=CRONUS IsBcSandbox=Y artifactUrl=https://bcartifacts-exdbf9fwegejdqak.
b02.azurefd.net/sandbox/26.1.33404.34384/us filesOnly=False
 ---> Running in e7b2e9537e83
 ---> Removed intermediate container e7b2e9537e83
 ---> 822c8bb2959f
Step 3/6 : COPY my /run/
 ---> 342700910c5e
Step 4/6 : COPY NAVDVD /NAVDVD/
 ---> ffe7cb5d379f
Step 5/6 : RUN \Run\start.ps1 -installOnly
 ---> Running in 6c53ae64cf7b
c:\run\my folder doesn't exist, creating it
Using DVD installer from C:\Run\260
Installing Business Central: multitenant=False, installOnly=True, filesOnly=False, includeTestToolkit=False, includeTestLibrariesOnly=False, includeTes
tFrameworkOnly=False, includePerformanceToolkit=False, appArtifactPath=, platformArtifactPath=, databasePath=, licenseFilePath=, rebootContainer=False
Installing from DVD
Starting Local SQL Server
Starting Internet Information Server
Copying Service Tier Files
C:\NAVDVD\ServiceTier\Program Files
C:\NAVDVD\ServiceTier\System64Folder
Copying Web Client Files
C:\NAVDVD\WebClient\Microsoft Dynamics NAV
Copying ModernDev Files
C:\NAVDVD
C:\NAVDVD\ModernDev\program files\Microsoft Dynamics NAV
Copying additional files
Copying ConfigurationPackages
C:\NAVDVD\ConfigurationPackages
Copying Test Assemblies
C:\NAVDVD\Test Assemblies
Copying Extensions
C:\NAVDVD\Extensions
Copying Applications
C:\NAVDVD\Applications
Copying Applications.US
C:\NAVDVD\Applications.US
Copying dependencies
Importing PowerShell Modules
Skipping restore of Cronus database
Modifying Business Central Service Tier Config File for Docker
Creating Business Central Service Tier
Installing SIP crypto provider: 'C:\Windows\System32\NavSip.dll'
Installation took 19 seconds
Installation complete
 ---> Removed intermediate container 6c53ae64cf7b
 ---> cb80141fea4c
Step 6/6 : LABEL legal="http://go.microsoft.com/fwlink/?LinkId=837447"       created="202505220642"       nav=""       cu=""       skipdatabase="Y"    
   country="US"       version="26.1.33404.34384"       platform="26.0.34304.0"
 ---> Running in 2922d2a26518
 ---> Removed intermediate container 2922d2a26518
 ---> 55ca6a8757a8
Successfully built 55ca6a8757a8
Successfully tagged dbcentral:sandbox-26.1.33404.34384-us-nodb
Building image took 208 seconds
Using image dbcentral:sandbox-26.1.33404.34384-us-nodb
Creating Container bcserver
Style: sandbox
Multitenant: No
Version: 26.1.33404.34384
Platform: 26.0.34304.0
Generic Tag: 1.0.2.64
Container OS Version: 10.0.20348.3566 (ltsc2022)
Host OS Version: 10.0.26100.4061 (24H2)
Host OS is 26100 (24H2) or above, recommended isolation mode is hyperv.
Using hyperv isolation
Using locale en-US
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Files in C:\ProgramData\BcContainerHelper\Extensions\bcserver\my:
- AdditionalOutput.ps1
- HelperFunctions.ps1
- MainLoop.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container bcserver from image dbcentral:sandbox-26.1.33404.34384-us-nodb
5c99b0e6ce1016019e289548996311d575d849840fd78249fb5c236b314bb4b9
Waiting for container bcserver to be ready
Initializing...
Setting host.docker.internal to 192.168.1.10 in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to 192.168.1.10 in container hosts file (copy from host hosts file)
Setting kubernetes.docker.internal to 127.0.0.1 in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to 172.26.48.1 in container hosts file
Starting Container
Hostname is bcserver
PublicDnsName is bcserver
Using NavUserPassword Authentication
Starting Internet Information Server
Import Encryption Key
[31;1mImport-NAVEncryptionKey: [0m
[31;1m[36;1mLine |[0m
[31;1m[36;1m[36;1m  15 | [0m     $output = [36;1mImport-NAVEncryptionKey @cmdletArgs[0m;[0m
[31;1m[36;1m[36;1m[0m[36;1m[0m[36;1m     | [31;1m               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~[0m
[31;1m[36;1m[36;1m[0m[36;1m[0m[36;1m[31;1m[31;1m[36;1m     | [31;1mSystem table $ndo$dbproperty is missing or database copy_prod_18APR2025 i
s not a Dynamics 365 Business Central application database.[0m

at <ScriptBlock>, C:\Run\SetupDatabase.ps1: line 152
at <ScriptBlock>, C:\Run\navstart.ps1: line 141
at <ScriptBlock>, C:\Run\start.ps1: line 391
at <ScriptBlock>, <No file>: line 1Error
Initializing...
Setting host.docker.internal to 192.168.1.10 in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to 192.168.1.10 in container hosts file (copy from host hosts file)
Setting kubernetes.docker.internal to 127.0.0.1 in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to 172.26.48.1 in container hosts file
Starting Container
Hostname is bcserver
PublicDnsName is bcserver
Using NavUserPassword Authentication
Starting Internet Information Server
Import Encryption Key
[31;1mImport-NAVEncryptionKey: [0m
[31;1m[36;1mLine |[0m
[31;1m[36;1m[36;1m  15 | [0m     $output = [36;1mImport-NAVEncryptionKey @cmdletArgs[0m;[0m
[31;1m[36;1m[36;1m[0m[36;1m[0m[36;1m     | [31;1m               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~[0m
[31;1m[36;1m[36;1m[0m[36;1m[0m[36;1m[31;1m[31;1m[36;1m     | [31;1mSystem table $ndo$dbproperty is missing or database copy_prod_18APR2025 i
s not a Dynamics 365 Business Central application database.[0m

at <ScriptBlock>, C:\Run\SetupDatabase.ps1: line 152
at <ScriptBlock>, C:\Run\navstart.ps1: line 141
at <ScriptBlock>, C:\Run\start.ps1: line 391
at <ScriptBlock>, <No file>: line 1
New-BcContainer Telemetry Correlation Id: 034ec2c5-971e-43a2-b3fd-90343484a66d
Initialization of container bcserver failed
At C:\Users\ganes\Documents\WindowsPowerShell\Modules\BcContainerHelper\6.1.3\ContainerHandling\Wait-NavContainerReady.ps1:42 char:17
+ ...             throw "Initialization of container $containerName failed" ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Initialization ...bcserver failed:String) [], RuntimeException
    + FullyQualifiedErrorId : Initialization of container bcserver failed
 

...

Screenshots

Image

Additional context

  • does it happen all the time?
  • did it use to work?

manjunathan-ganesan avatar May 23 '25 09:05 manjunathan-ganesan

We've found some similar issues:

  • #2801 , similarity score: 89%
  • #1518 , similarity score: 88%
  • #2663 , similarity score: 88%
  • #1754 , similarity score: 86%
  • #1162 , similarity score: 86%
  • #3247 , similarity score: 85%
  • #3242 , similarity score: 84%
  • #3481 , similarity score: 83%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

similar-issues-ai[bot] avatar May 23 '25 09:05 similar-issues-ai[bot]

From the error it sounds like something is off with the database. System table $ndo$dbproperty is missing or database copy_prod_18APR2025 is not a Dynamics 365 Business Central application database.

  • Have you been able to run Business Central on this database before?
  • How did you copy the database? Did you follow these steps? https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-database-export
  • Does it work if you try to spin up a container using the -bakFile '<Path or Secure Url of a bakFile if you want to restore a database in the container>' parameter?

aholstrup1 avatar May 23 '25 11:05 aholstrup1

Yes, our production Business Central environment is already running on that database. We created a backup from it using the .bacpac method, following the steps in the link you provided.

This is our first time trying to spin up a dev/sandbox container using that database. Since the backup was created as a .bacpac, we haven't used the -bakFile parameter, as it's not applicable here.

Please let me know if there’s anything specific we should check when connecting a container to an Azure SQL database restored from a .bacpac file.

manjunathan-ganesan avatar May 23 '25 12:05 manjunathan-ganesan

Creating a container from an online backup is not "just" something you do. I wrote this blog post a few years ago https://freddysblog.com/2021/03/02/restoring-your-online-business-central-database-locally/

Haven't tried it recently, but it isn't just mounting the database. The database backup you receive is a tenant database without the apps.

freddydk avatar May 23 '25 14:05 freddydk

Hi @freddydk , Thanks for your response. Let me try the blogs and will keep you posted the updates.

manjunathan-ganesan avatar May 26 '25 07:05 manjunathan-ganesan

Hi @freddydk , I have followed the blog which you have suggested but still I am getting following error. The .bacpac file is around 8GB.

++++++++++++++++++++++++++ Exception calling "ImportBacpac" with "2" argument(s): "Data cannot be imported into target because it contains one or more user obj ects. Import should be performed against a new, empty database. Warning SQL0: The source contains users that rely on an external authentication provider that is not supported by the target. These users will be treated as users without logins. Error SQL0: Data cannot be imported into target because it contains one or more user objects. Import should be performed against a n ew, empty database. " Exception Script Stack Trace: at Restore-BacpacWithRetry, C:\run\HelperFunctions.ps1: line 96 at <ScriptBlock>, <No file>: line 39 PowerShell Call Stack: at Invoke-ScriptInBcContainer, C:\Users\ganes\Documents\WindowsPowerShell\Modules\BcContainerHelper\6.1.3\ContainerHandling\Invoke-S criptInNavContainer.ps1: line 71 at <ScriptBlock>, C:\Users\ganes\Desktop\Untitled29.ps1: line 56 Container Free Physical Memory: 10.0Gb Disk C: Free 113Gb from 127Gb Services in container bcserver3:

  • MicrosoftDynamicsNavServer$BC is Running
  • MSSQL$SQLEXPRESS is Running Relevant event log from container bcserver3:
  • 20250603 04:19:37 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 04:19:37 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:19:37 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:17:01 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 04:17:01 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:17:01 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:14:25 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 04:14:25 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:14:25 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:11:50 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 04:11:50 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:11:50 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:09:16 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 04:09:16 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:09:16 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:06:42 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 04:06:42 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:06:42 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:04:08 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 04:04:08 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:04:08 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:01:34 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 04:01:34 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 04:01:34 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:59:00 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 03:59:00 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:59:00 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:57:21 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 03:57:21 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:57:21 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:56:13 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 03:56:13 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:56:13 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:55:21 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 03:55:21 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:55:21 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:54:37 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 03:54:37 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:54:37 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:53:55 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 03:53:55 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:53:55 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:53:16 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 03:53:16 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:53:16 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:52:38 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 03:52:38 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:52:38 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:51:58 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 03:51:58 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:51:58 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:51:21 - MSSQL$SQLEXPRESS Could not allocate a new page for database 'Production' because the 'PRIMARY' filegroup is full due to lack of storage space or da tabase files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by d ropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the fileg roup.
  • 20250603 03:51:21 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:51:21 - MSSQL$SQLEXPRESS CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
  • 20250603 03:12:00 - MicrosoftDynamicsNAVClientWebClient Category: Microsoft.Dynamics.Framework.UI.WebBase.ClientExceptionStateProcessingStrategy EventId: 0 ConnectionId: 0HND2GATGQEJ5 RequestId: 0HND2GATGQEJ5:0000000D RequestPath: /BC/csh TransportConnectionId: xZMsgxfJUYR_tibpsGXIPg The session has timed out or could not be found. Exception: Microsoft.Dynamics.Framework.UI.InvalidSessionException: The session has timed out or could not be found. at Microsoft.Dynamics.Framework.UI.WebBase.ClientSessionBase.EnterProcessing(RequestContext requestContext, Boolean updateLastU sedTimestamp, IExceptionHandler exceptionHandler, CancellationToken token, Boolean startLogicalThread) in s:\repo\src\Platform\Clien t\Web\Prod.Client.WebBase\Session\ClientSessionBase.cs:line 763 at Microsoft.Dynamics.Framework.UI.CultureAwaiter.GetResult() in s:\repo\src\Platform\Client\Shared\Prod.ClientFwk\Threading\As ync\CultureAwaiter.cs:line 66 at Microsoft.Dynamics.Framework.UI.WebBase.IdleMessageHandler.ProcessOneMessage() in s:\repo\src\Platform\Client\Web\Prod.Clien t.WebBase\Session\IdleMessageHandler.cs:line 200 Exception calling "ImportBacpac" with "2" argument(s): "Data cannot be imported into target because it contains one or more user objects. Import should be performed against a new, empty database. Warning SQL0: The source contains users that rely on an external authentication provider that is not supported by the target. These users will be treated as users without logins. Error SQL0: Data cannot be imported into target because it contains one or more user objects. Import should be performed against a new, empty database. " At C:\Users\ganes\Documents\WindowsPowerShell\Modules\BcContainerHelper\6.1.3\ContainerHandling\Invoke-ScriptInNavContainer.ps1:113 char:13
  •         throw $errorMessage

  •         ~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : OperationStopped: (Exception calli...ty database. ":String) [], RuntimeException
    • FullyQualifiedErrorId : Exception calling "ImportBacpac" with "2" argument(s): "Data cannot be imported into target because
      it contains one or more user objects. Import should be performed against a new, empty database. Warning SQL0: The source contains users that rely on an external authentication provider that is not supported by the target.
      These users will be treated as users without logins. Error SQL0: Data cannot be imported into target because it contains one or more user objects. Import should be performed again st a new, empty database. "==================================

manjunathan-ganesan avatar Jun 05 '25 10:06 manjunathan-ganesan

Hi @freddydk ,

Please let me know if you have suggestions for the above error.

manjunathan-ganesan avatar Jun 20 '25 06:06 manjunathan-ganesan

Hi @freddydk ,

Please let me know if you have any inputs on the above error.

manjunathan-ganesan avatar Jun 23 '25 13:06 manjunathan-ganesan