web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / Sync-NAVTenant Fails D...
Small and medium business | Business Central, N...
Suggested Answer

Sync-NAVTenant Fails During Data Upgrade from NAV 2017 to BC 25 (Large DB – SQL Connection Lost)

(2) ShareShare
ReportReport
Posted on by CU07120751-1 4

Hello Community,

We are currently performing a data upgrade from NAV 2017 to Business Central (BC) 25.Following Microsoft’s documented upgrade path, we successfully converted the database from NAV 2015 → BC 14 as the required intermediate step. We are now working on the next stage: converting from BC 14 → BC 25.

However, we are encountering a major issue during the upgrade.

Issue Description
When running the Sync-NAVTenant command on the BC 25 environment, the process runs for several hours and eventually fails with the following error:

Sync-NAVTenant :
Sync-NAVTenant:
Line |
15 | $output = Sync-NAVTenant @cmdletArgs;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
| The SQL Server connection is no longer available.

At line:2 char:1
+ Sync-NAVTenant -ServerInstance BC252 -Mode sync -Tenant default
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Sync-NAV...vailable.:String) [Sync-NAVTenant], InvalidOperationException
+ FullyQualifiedErrorId : navId,Microsoft.Dynamics.Nav.Management.SyncNAVTenant

 

Environment Details
 

Upgrade Path: NAV 2017 → (via NAV 2015) → BC 14 → BC 25
Database Size: ~330 GB (quite large)

The Sync-NAVTenant step runs for hours and then drops the SQL connection.

Categories:
Dynamics 365 Business Central
2025-12-07_12-59-...
I have the same question (0)
  • Suggested answer
    Assisted by AI
    OussamaSabbouh Profile Picture
    OussamaSabbouh 5,379 on at
    Hello,
     
    Your Sync-NAVTenant fails because SQL is blocking the schema sync on your huge 330-GB DB.
    It waits for hours, hits a lock timeout, and BC reports “SQL Server connection is no longer available”.
    Fixes that usually work:
    Stop all BC/NAV services and make sure no other session touches the DB.
    Disable SQL jobs during sync.
    Run with:
    Sync-NAVTenant -ServerInstance BC252 -Tenant default -Mode Sync -CommitPerTable

    Increase DatabaseLockTimeout and SQLCommandTimeout on the BC 25 service.
    After that, the sync normally completes.
     
    Regards,
    Oussama Sabbouh
  • Gerardo Rentería García Profile Picture
    Gerardo Rentería Ga... 25,154 Most Valuable Professional on at
    Hi Could you try again by increasing resources on the server?
    Best
    GR

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,316

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 2,449 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,431 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans