Installing BC on docker fails due to wrong SQL version

(7) Share

Report

Posted on by NotAvailable

Hi,

we stumbled upon an issue recently when creating new BC docker containers (via BcContainerHelper), where the deploy stops while restoring the cronus database to the newly created container.

Restoring CRONUS Demo Database
The database was backed up on a server running version 16.00.4210. That version is incompatible with this server, which is running version 15.00.4430. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.
RESTORE DATABASE is terminating abnormally.

Is this related to an issue with BC docker image or something more general, i.e. BcContainerHelper?

Categories:

Dynamics 365 Business Central

docker bc sql err...

I have the same question (0)

All responses (7)

Answers (1)

Suggested answer

Sumit Singh 6,274 on at

Like (1)

Report
Installing BC on docker fails due to wrong SQL version

Hi,

I think as mentioned in the comments below, alwaysPull might fix this, but only if your local cache is pulling an older generic image (SQL 2019 / v15) while the CRONUS backup in newer artifacts was created on SQL 2022 / v16. Forcing a fresh pull gets the latest generic image with SQL 2022, so the restore succeeds. Microsoft explicitly recommended using -alwaysPull when they switched BC generic images to SQL 2022.
You can try:

Re-run your container creation and add -alwaysPull to New-BcContainer to fetch the newest generic image (with SQL 2022).

Ensure you follow the standard container setup guidance and keep BcContainerHelper and images up to date.

If you still hit the error after -alwaysPull, pin artifacts/generic image that match SQL 2022, or remove the old generic image from your local cache and pull again.
References
[1] BC generic images switch to SQL Server 2022 - GitHub
[2] Restore a Database Backup Using SSMS - SQL Server
[3] Running a container-based development environment" - Business Central ...

Mark the Boolean true “Does this answer your Question” if this was Helpful.

Was this reply helpful? Yes No
Suggested answer

Jeffrey Bulanadi 8,429 on at

Like (1)

Report
Installing BC on docker fails due to wrong SQL version

Hi,

This is a classic issue between the SQL Server version used to back up the CRONUS database and the one running inside your Docker container. Business Central containers rely on SQL compatibility, and when the backup is from a newer SQL version than the container supports, the restore will fail with the error you’re seeing.

Here’s how to resolve it:

The CRONUS database you’re trying to restore was backed up on SQL Server version 16.00.4210, but your container is running version 15.00.4430. SQL Server does not support restoring databases from newer versions into older ones.

You have two options:

Use a backup file that was created on SQL Server 2019 (version 15) or earlier.

Explicitly specify a newer SQL Server instance when creating the container using -sqlInstance 'MySQL16' in your New-BCContainer command.

If you’re running Windows 11, consider using the -useBestContainerOS parameter. This will attempt to select the most compatible container OS version (e.g., LTSC2022), which may include support for newer SQL versions.

Always verify the SQL version compatibility between your host, container image, and backup file before deploying.

Helpful Reference
SQL Server Version Mismatch – GitHub Issue #3965
Running a Container-Based Development Environment – Microsoft Learn
Troubleshooting BcContainerHelper Docker Build Errors – Steve Endow Blog
Running Business Central in Docker using SQL on the host | Freddys blog

If you find this helpful, feel free to mark this as the suggested or verified answer.

Cheers
Jeffrey

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 19,135 Super User 2025 Season 2 on at

Like (3)

Report

Installing BC on docker fails due to wrong SQL version

Not sure but just check it if this helps:https://blog.steveendow.com/2020/04/business-central-docker-containers-make.html

https://community.dynamics.com/blogs/post/?postid=4d497465-467c-4282-8b0e-eed67f53dbbe

Was this reply helpful? Yes No
Verified answer

NotAvailable 36 on at

Like (2)

Report

Installing BC on docker fails due to wrong SQL version

Adding -alwaysPull parameter to the New-BCContainer command seems to solve the problem.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 92,161 Super User 2025 Season 2 on at

Like (3)

Report

Installing BC on docker fails due to wrong SQL version

Hi, I've seen similar questions in the BC Yammer Group recently, and I hope the following information can give you some hints.

https://www.yammer.com/dynamicsnavdev/threads/3374171507621888

BC generic images switch to SQL Server 2022 · Issue #3962 · microsoft/navcontainerhelper

Thanks.

ZHU

1 people found this reply helpful.

Was this reply helpful? Yes No
NotAvailable 36 on at

Like (3)

Report

Installing BC on docker fails due to wrong SQL version

@Bilal Haider,
as mentioned in the post, this is a Business Central Docker image.

the Sql server installed is part of the image itself. There is no SQL server installed separately.

the image is retrieved using the below (normal) command

$ArtifactUrl = Get-BCArtifactUrl -type Sandbox -country se -select latest

Was this reply helpful? Yes No
Suggested answer

Bilal Haider 408 on at

Like (3)

Report

Installing BC on docker fails due to wrong SQL version

Hi,

Main reason for this error is that the backup taken on a newer sql server version cannot be restored on an older sql server version.

Now to resolve there are many ways:

1) Change you backup file, use any file that is backed up on 15 or before.

2) Use any sql server isntance installed on your computer and explicitly mention in command New-BCContainer to use that sql instance

-sqlInstance 'MySQL16' `

3) If you are running Windows 11 then use parameter -useBestContainerOS it will pick the ltsc2022 if possible

If the issues still not resolved then please share the script you are using.

Was this reply helpful? Yes No