[Bug]: Import FOB object fails: The following ODBC error occurred:

[epernst]

BCContainerhelper version

6.1.6

Describe the issue

Creating a new v.14 container with test objects fails with an SQL/ODBC error. I assume it has something to do with the shift to SQL 2022?

Command or script used to produce the issue

$ArtURL = Get-BCArtifactUrl -type OnPrem -country w1 -version 14.44 -select Latest
$Params = @{
accept_eula = $true
accept_insiderEula = $true
accept_outdated = $true
artifactUrl = $ArtURL
containerName = 'testdownload'
imageName = 'myImageName'
includeTestLibrariesOnly = $true
includeTestToolkit = $true
doNotExportObjectsToText = $true
}
New-BcContainer @params

Full output of the command or script

Downloading Platform index to C:\Users\eper\AppData\Local\Temp\bcContainerHelper.platform.json
Downloading w1 index to C:\Users\eper\AppData\Local\Temp\bcContainerHelper.w1.json
BcContainerHelper is version 6.1.6
BcContainerHelper is not running as administrator
Host is Microsoft Windows 11 Pro - 10.0.26100.4351
UsePsSession is True
UsePwshForBc24 is True
UseWinRmSession is never
UseSslForWinRmSession is True
Docker Client Version is 27.3.1
Docker Server Version is 27.3.1
Removing Desktop shortcuts
Fetching all docker images
Fetching all docker volumes
ArtifactUrl and ImageName specified
Image myimagename:onprem-14.44.49619.0-w1 already exists
Using image myimagename:onprem-14.44.49619.0-w1
Creating Container testdownload
Style: onprem
Multitenant: No
Version: 14.44.49619.0
Platform: 14.0.49616.0
Generic Tag: 1.0.2.71
Container OS Version: 10.0.26100.4349 (ltsc2025)
Host OS Version: 10.0.26100.4351 (24H2)
Host OS is 26100 (24H2) or above, recommended isolation mode is hyperv. HyperV state is unknown, if you encounter problems you might need to install 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\testdownload\my:

• AdditionalOutput.ps1
• HelperFunctions.ps1
• MainLoop.ps1
• SetupVariables.ps1
• updatecontainerhosts.ps1
  Creating container testdownload from image myimagename:onprem-14.44.49619.0-w1
  e45c63a3da24202544507244d2f00dde5c511af92d9b23ee16a6a65a0f9ce368
  Waiting for container testdownload to be ready
  Initializing...
  Setting host.containerhelper.internal to 172.17.192.1 in container hosts file
  Starting Container
  Hostname is testdownload
  PublicDnsName is testdownload
  Using Windows Authentication
  Starting Local SQL Server
  Starting Internet Information Server
  Modifying Service Tier Config File with Instance Specific Settings
  Starting Service Tier
  Registering event sources
  Creating DotNetCore Web Server Instance
  Using application pool name: NAV
  Using default container name: NavWebApplicationContainer
  Copy files to WWW root C:\inetpub\wwwroot\NAV
  Create the application pool NAV
  Create website: NavWebApplicationContainer without SSL
  Update configuration: navsettings.json
  Done Configuring Web Client
  Creating http download site
  Creating Windows user eper
  Setting SA Password and enabling SA
  Creating SUPER user
  Container IP Address: 172.17.204.123
  Container Hostname : testdownload
  Container Dns Name : testdownload
  Web Client : http://testdownload/NAV/
  Dev. Server : http://testdownload
  Dev. ServerInstance : NAV

Files:
http://testdownload:8080/ALLanguage.vsix

Container Total Physical Memory is 8.5Gb
Container Free Physical Memory is 6.4Gb

Initialization took 79 seconds
Ready for connections!
Reading CustomSettings.config from testdownload
Creating Desktop Shortcuts for testdownload
Importing Objects from C:\TestToolKit\CALTestLibraries.W1.fob (container path)
Import-TestToolkitToBcContainer Telemetry Correlation Id: 4f8f99a8-1ba7-4e11-90ad-167b9bc2bd2b
New-BcContainer Telemetry Correlation Id: 6c3325a6-3dc2-4e1a-8dd7-e3aa3cfe07bb
docker : Import-NAVApplicationObject : : [22922069] The following ODBC error occurred:
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.1.6\ContainerHandling\Invoke-ScriptInNavContainer.ps1:295 char:17

• ... docker exec $containerName $shell $containerFile | Out-H ...

•              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : NotSpecified: (Import-NAVAppli...error occurred::String) [], RemoteException
  • FullyQualifiedErrorId : NativeCommandError

Additional information

This worked a few weeks ago - until the SQL 2022 update?

Does this happen every time?

Yes

Did this used to work?

Yes

[superbernd]

We running into same problem. Is there a solution or fix?

[AUmanskis]

Same issue for me. tried with multiple BCContainerHelper versions (6.1.0, 6.1.6, 6.1.7-preview1336)
Did somebody solve issue?

Checked all ODBC drivers on container and host. All is good

[hugifreyr]

Same error here and all our BC 14 build are unable to work because of this. Hope this solves asap

[veljo09]

Same error on my side.

Export-NAVApplicationObject : : [22922069] The following ODBC error occurred:
Error: [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
tate ID: IM002

[aholstrup1]

@epernst It likely is related to the SQL 2022 move.

As a workaround you can try using one of the older images that have SQL 2019. E.g. use this generic image:
-useGenericImage "mcr.microsoft.com/businesscentral:10.0.26100.4061" for the ltsc2025 image
And
-useGenericImage "mcr.microsoft.com/businesscentral:10.0.20348.3692" for the ltsc2022 image

[AUmanskis]

Thank you @aholstrup1, that extra property helped me :)

[kaspermoerch]

@epernst It likely is related to the SQL 2022 move.

As a workaround you can try using one of the older images that have SQL 2019. E.g. use this generic image: -useGenericImage "mcr.microsoft.com/businesscentral:10.0.26100.4061" for the ltsc2025 image And -useGenericImage "mcr.microsoft.com/businesscentral:10.0.20348.3692" for the ltsc2022 image

@aholstrup1 Which generic image should be used for ltsc2019 to get one with SQL 2019?

[aholstrup1]

@epernst It likely is related to the SQL 2022 move.
As a workaround you can try using one of the older images that have SQL 2019. E.g. use this generic image: -useGenericImage "mcr.microsoft.com/businesscentral:10.0.26100.4061" for the ltsc2025 image And -useGenericImage "mcr.microsoft.com/businesscentral:10.0.20348.3692" for the ltsc2022 image

@aholstrup1 Which generic image should be used for ltsc2019 to get one with SQL 2019?

ltsc2019: -useGenericImage "mcr.microsoft.com/businesscentral:10.0.17763.7314"

ltsc2016: -useGenericImage "mcr.microsoft.com/businesscentral:10.0.14393.8066"