Server migration from 2019 to 2022 failed

Question

Server migration from 2019 to 2022 failed

Anonymous

Dear Team,

We are upgrading our web application server(2019 Standard) to 2022 Standard, during initial setup, it fails at 87% and automatically closing the migration window.

I'm attaching the logs, could you please help us.

2024-11-20 01:15:33, Info MIG COutOfProcPluginFactory::FreeSurrogateHost: Shutdown in progress.

2024-11-20 01:15:33, Info MIG MigHost: Exiting process.

2024-11-20 01:15:33, Info MIG COutOfProcPluginFactory::LaunchSurrogateHost::CommandLine: "C:$WINDOWS.~BT\Sources\mighost.exe" {E1ACDAEB-A9D7-49E5-81BF-C3B142C4A4DC} /InitDoneEvent:MigHost.{E1ACDAEB-A9D7-49E5-81BF-C3B142C4A4DC}.Event /ParentPID:13776 /LogDir:"C:$WINDOWS.~BT\Sources\Panther"

2024-11-20 01:15:33, Info MIG MigHost started with command line: {E1ACDAEB-A9D7-49E5-81BF-C3B142C4A4DC} /InitDoneEvent:MigHost.{E1ACDAEB-A9D7-49E5-81BF-C3B142C4A4DC}.Event /ParentPID:13776 /LogDir:"C:$WINDOWS.~BT\Sources\Panther"

2024-11-20 01:15:33, Info MIG MigHost: CMigPluginSurrogate::Init: Successfully initialized surrogate.

2024-11-20 01:15:33, Info MIG MigHost: Initialized successfully with CLSID[{E1ACDAEB-A9D7-49E5-81BF-C3B142C4A4DC}] and LogDir=[C:$WINDOWS.~BT\Sources\Panther]

2024-11-20 01:15:33, Info MIG COutOfProcPluginFactory::LaunchSurrogateHost: Successfully launched host and got control object.

2024-11-20 01:15:33, Info [0x080489] MIG Setting system object filter context (User)

2024-11-20 01:15:33, Info MIG Attempting to add direct mapping for HKCU to 0x80000003, S-1-5-21-246945237-1012691781-900129635-5321

2024-11-20 01:15:33, Info [0x0803df] MIG Adding direct mapping from HKCU to HKEY_USERS\S-1-5-21-246945237-1012691781-900129635-5321 (R/W)

2024-11-20 01:15:33, Info [0x0803e1] MIG Successfully mapped HKCU

2024-11-20 01:15:33, Info MIG Direct mapping found the appropriate key, proceeding

2024-11-20 01:15:33, Info MIG Adding indirect mapping for HKCU\Software\Classes (C:\Users\schs-galaxy\AppData\Local\Microsoft\Windows\UsrClass.dat) to 0x80000003, S-1-5-21-246945237-1012691781-900129635-5321_Classes

2024-11-20 01:15:33, Info [0x0803e2] MIG Adding indirect mapping from HKCU\Software\Classes to <C:\Users\schs-galaxy\AppData\Local\Microsoft\Windows\UsrClass.dat> loaded at HKEY_USERS\S-1-5-21-246945237-1012691781-900129635-5321_Classes (R/W)

2024-11-20 01:15:33, Info [0x0803e4] MIG Successfully mapped HKCU\Software\Classes

2024-11-20 01:15:33, Info [0x08040f] MIG Setting SMI registry mappings for user context (HKU\S-1-5-21-246945237-1012691781-900129635-5321, HKU\S-1-5-21-246945237-1012691781-900129635-5321_Classes)

2024-11-20 01:15:33, Info [0x080489] MIG Setting system object filter context (User)

2024-11-20 01:15:33, Info MIG Attempting to add direct mapping for HKCU to 0x80000003, S-1-5-21-246945237-1012691781-900129635-5321 (1)

2024-11-20 01:15:33, Info [0x0803df] MIG Adding direct mapping from HKCU to HKEY_USERS\S-1-5-21-246945237-1012691781-900129635-5321 (1) (R/W)

2024-11-20 01:15:33, Info [0x0803e1] MIG Successfully mapped HKCU

2024-11-20 01:15:33, Info MIG Direct mapping found the appropriate key, proceeding

2024-11-20 01:15:33, Info MIG Adding indirect mapping for HKCU\Software\Classes (C:$WINDOWS.~BT\NewOS\Users\schs-galaxy\AppData\Local\Microsoft\Windows\UsrClass.dat) to 0x80000003, S-1-5-21-246945237-1012691781-900129635-5321_Classes (1)

2024-11-20 01:15:33, Info [0x0803e2] MIG Adding indirect mapping from HKCU\Software\Classes to <C:$WINDOWS.~BT\NewOS\Users\schs-galaxy\AppData\Local\Microsoft\Windows\UsrClass.dat> loaded at HKEY_USERS\S-1-5-21-246945237-1012691781-900129635-5321_Classes (1) (R/W)

2024-11-20 01:15:33, Info [0x0803e4] MIG Successfully mapped HKCU\Software\Classes

2024-11-20 01:35:27, Warning [0x08094f] MIG MigHost: CMigPluginSurrogate::WaitForHostTermination: Parent process unexpectedly exited. Terminating host.

2024-11-20 01:35:27, Info MIG MigHost: Exiting process.

Thanks,

Shabin

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

Accepted answer

5 additional answers

Answer 1

Anonymous

Hello Shabin,

sorry for my helpless advice.

The issue you're experiencing seems complicated. It is recommended contact Microsoft support team for further assistant.

Here is the link: Customer service phone numbers - Microsoft Support.

Regards,

Lei

Answer 2

Hello Shabin,

according to the screenshots you added, the possible causes and solutions:

Exception code '0xc0000409' usually indicates a stack buffer overflow, which may be due to a memory issue. We recommend that you run the memory diagnostic tool to check whether there is a problem with the memory.

Run the following command at the command prompt:

mdsched

Then select Reboot and check the memory.

ntdll.dll file corruption
- 'ntdll.dll' is a critical system file, and any corruption can cause the app to crash.
- Solution: Run the System File Checker tool.
  - Open a command prompt (administrator mode) and run the following command:
sfc /scannow
Misconfigurations or inconsistencies can cause the migration process to fail. Make sure to make sure that the system is set up and configured correctly and that the necessary services are not disabled.
Perform a clean boot to run the system with minimal boot programs and drivers with fewer distractions.

Answer 3

Hi Shabin Suresh1,

thank you for posting on the Microsoft Community Forums.

Log analysis is not be supported in this forum, however, here are still some general steps you can refer to:

Check for Compatibility Issues: Ensure that all installed applications and services on your current server are compatible with Windows Server 2022.
Update System and Drivers: Make sure your current server (2019 Standard) is fully updated with the latest patches and drivers. Sometimes, outdated system files can cause issues during major upgrades.
Disable Antivirus/Firewall: Sometimes, security software can interfere with the upgrade process. Temporarily disable your antivirus and firewall during the upgrade to see if that resolves the issue.
Check Disk Space: Ensure that there is enough free disk space on your server to accommodate the upgrade process. Running out of disk space can cause the upgrade to fail.
Run Upgrade Troubleshooter: Windows provides a built-in troubleshooter for upgrade issues. Running this tool might help identify and resolve the problem.
Ensure that your hardware meets the requirements for Windows Server 2022: Hardware requirements for Windows Server | Microsoft Learn.

Hope it helps.

Best regards,

Lei

Answer 4

Hi Shabin Suresh1,

thank you for posting on the Microsoft Community Forums.

Log analysis is not be supported in this forum, however, here are still some general steps you can refer to:

Check for Compatibility Issues: Ensure that all installed applications and services on your current server are compatible with Windows Server 2022.

Update System and Drivers: Make sure your current server (2019 Standard) is fully updated with the latest patches and drivers. Sometimes, outdated system files can cause issues during major upgrades.

Disable Antivirus/Firewall: Sometimes, security software can interfere with the upgrade process. Temporarily disable your antivirus and firewall during the upgrade to see if that resolves the issue.

Check Disk Space: Ensure that there is enough free disk space on your server to accommodate the upgrade process. Running out of disk space can cause the upgrade to fail.

Run Upgrade Troubleshooter: Windows provides a built-in troubleshooter for upgrade issues. Running this tool might help identify and resolve the problem.

Ensure that your hardware meets the requirements for Windows Server 2022: Hardware requirements for Windows Server | Microsoft Learn.

Hope it helps.

Best regards,

Lei

Dear Lei Tao,

Good day!

Let me confirm these points and get back to you.

Thank you for the support!

Answer 5

Anonymous

Hi Lei,

This the error while upgrade, could you please check.

Thanks,

Shabin

Share via

Server migration from 2019 to 2022 failed

5 additional answers