Error on upgrade NAV2018 to 365BC

Business Central/NAV Technical Forum
1

I am trying to upgrade a NAV2018 database to 365BC.

I follow the MS description as found here

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrading-the-data#UploadLicense

Everything works fine until Task 11, Synchronization.

It runs for a short while and then ends with the following error:

“Sync-NAVTenant : A dead connection cannot be brought back to the livings”

It should not be a SQL time out as the error shows up quickly and it is a very small database.

If I look in the Event log, I find the following SQLSERVER-error:

“A user request from the session with SPID 56 generated a fatal exception. SQL Server is terminating this session. Contact product Support Services with the dump produced in the log directory.”

EventID 17310, Qualifiers 49152

I have tried the proces on two different machines and get the same result. Using SQL Server 2016.

The NAV2018 database works fine and operational. I can compile all objects and synchronize before I start the upgrade.

Anyone, any ideas ?

Kind regards

2

Hi,

Funny error message!! [emoticon:c4563cd7d5574777a71c318021cbbcc8]

How big is the database?

If its a large database, then it may help to increase the “SQL command timeout”.

3

Hi,

A very small database. Actually just a demodatabase, we are using.

However, today I got the problem solved :slight_smile:

I uninstalled my 365BC and installed 365BC ***.upd. 5 and went through the whole proces once again.

This time without any problems, so now we have a new demo-database without recreating demodata :slight_smile:

Well, seen strange issues before.

Don’t spend all energy on the RTM- and first ***.updates. Wait some months, and you avoid a lot of unnecessary grey hair :wink:

4

Happy you solved it. [emoticon:c4563cd7d5574777a71c318021cbbcc8]

Did you remember to update your NAV 2018 to the latest CU first?

Not sure I agree you should avoid RTM versions, with two major releases per year, that’s two RTM’s. But if you don’t, then you should make sure you apply the CU’s when they are released (even if you only update the platform).