[SOLVED] Server 2016 upgrade to 2019 failed in-place upgrade "... error during MIGRATE_DATA operation"

[ceez]

Hello everyone.

So I have a Windows 2016 Standard Server that is also running SQL 2016. I need to upgrade this server to 2019 Standard. Before I continue though, as of yesterday we were trying to go from 2012R2 to 2019 which was failing with the same error. For giggles I decided to test in-place to 2016 and that one worked fine. Now I am trying to continue my path to 2019. With that said, here's the error when I log back in after it has gone through the entire installation and multiple reboots:

0x8007001F -0x4000D
The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation

I have scavenged the setupact.log and setuperr.log and compdata...xml file with no luck. At first I thought it was profile accounts that the SQL servers create because I was seeing this

2023-05-24 17:06:51, Error [0x0803b6] MIG Can't retrieve group information for user NT SERVICE\SSASTELEMETRY. NetUserGetLocalGroups failed 0x000008AD
2023-05-24 17:06:51, Error [0x0803b6] MIG Can't retrieve group information for user NT SERVICE\SSISTELEMETRY130. NetUserGetLocalGroups failed 0x000008AD
2023-05-24 17:06:57, Error [0x0803b6] MIG Can't retrieve group information for user NT SERVICE\ReportServer$MSSQLSERVER2016. NetUserGetLocalGroups failed 0x000008AD
2023-05-24 17:06:57, Error [0x0803b6] MIG Can't retrieve group information for user NT SERVICE\SQLTELEMETRY. NetUserGetLocalGroups failed 0x000008AD
2023-05-24 17:06:57, Error [0x0803b6] MIG Can't retrieve group information for user NT SERVICE\MSSQLFDLauncher. NetUserGetLocalGroups failed 0x000008AD
2023-05-24 17:06:57, Error [0x0803b6] MIG Can't retrieve group information for user NT SERVICE\MsDtsServer130. NetUserGetLocalGroups failed 0x000008AD

Removed the profiles - no luck and no longer showing up in the error log after future upgrade attempts

In the compdata file it was pointing to two inf files....the usual culprits which sometimes impair Win10 version upgrades....the XPS document writer and microsoft pdf writer. Got rid of those....no luck and no longer showing up in the compdata xml after future upgrade attempts.

AV is disabled before starting the installation. All SQL services are stopped and even disabled. There's nothing else running on this server but it's being a PITA!

Other than the setupact and setuperr log file (zip attached), what can I share with you guys to get help with this in-place upgrade?

Thanks!

 

[ceez]

I think I solved the issue - I have to attempt to replicate it first to confirm, but there was a Dynamics related service that I had missed on this server. I stopped and disabled the service and re-ran the in-place and it completed successfully.
Now as a full test going to revert to the 2012R2 snapshot and try it again by stop\disabling that service.

 

[ceez]

So the problem was a Dynamics service that was missed. After stopping and disabling this service (along with all other SQL services) I was able to in-place upgrade from 2012R2 to 2019.