error while migrating database to Azure SQL

The screenshots show that the self-hosted Integration Runtime is installed, but the node is not actually registered to the migration service. In this state, Azure Database Migration Service shows Integration Runtime not registered and the migration scenario stays disabled.

Use this recovery path:

1. Uninstall the existing Integration Runtime from Control Panel.
   • During uninstall, select Yes to delete all user data.
   • This matters because existing registered nodes cannot be re-registered to another integration runtime without uninstalling first.
2. Install the Integration Runtime again using the latest installer.
   • If needed, download the latest MSI from the Microsoft Download Center.
3. Register it again using the authentication key from the Azure portal.
   • The presence of keys in the portal only means the service generated keys; it does not mean the local node is registered.
4. If registration still fails, check the Integration Runtime event log on the machine.
   • The documented guidance is to review the IR event log for the exact registration failure.
   • If the event log shows UnauthorizedAccessException, verify the DIAHostService logon account in Windows Services.
   • Then verify that account has read/write permission to: %programdata%\Microsoft\DataTransfer\DataManagementGateway
5. If the service account was changed manually, use the supported fix:
   • Perform a clean uninstall of the current self-hosted IR.
   • Reinstall the self-hosted IR.
   • Then change the service account correctly after installation.
6. If the machine resolves localhost incorrectly during registration, use 127.0.0.1 instead of localhost.
7. For Database Migration Service registration, the Azure CLI command supports registering the Integration Runtime with the auth key:
   • az datamigration register-integration-runtime --auth-key <key>
   • If the command cannot detect the installed IR, the documented optional parameters include --installed-ir-path or --ir-path.

Important:

• Reinstalling repeatedly without deleting old IR user data can leave the node in a bad registration state.
• If the machine is a laptop/desktop that sleeps or hibernates, IR can enter an error state; reinstalling IR and disabling sleep/hibernate is recommended.
• Use the latest compatible IR version.

References:

• Troubleshoot self-hosted integration runtime
• Troubleshooting cloud migration
• az datamigration register-integration-runtime