Share via

Azure Migration via ADS is stuck 'Creating', self hosted integration runtime shows errors

TMADev 25 Reputation points
2025-10-03T12:05:54.05+00:00

I have used ADS to migrate this data previously (successfully) with locally hosted integration runtime. There are a couple of issues with views that can't be migrated (fine by me) but other than that, the migration goes through fine (all authentications, table selection etc are fine) using Azure Data Studio and joins a queue but never leaves the 'Creating' stage.

Looking at event logs, the Integration Runtime seems to be hitting a problem, looks like something to do with authentication. The error is:

System.MissingMethodException: Method not found: 'Void Microsoft.DataTransfer.TaskHosting.TaskInfo.set_AuthenticationHeaderProviderAsync(Microsoft.DataTransfer.Common.Models.AuthenticationHeaderProviderAsync)'.
   at Microsoft.DataTransfer.TaskManagement.TaskManagementClientConsumer.<GetMessagesInternalAsync>d__22.MoveNext()
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
   at Microsoft.DataTransfer.TaskManagement.TaskManagementClientConsumer.GetMessagesInternalAsync(Int32 messageCount, Nullable`1 workerId, Nullable`1 activityId, Nullable`1 availableWeight)
   at Microsoft.DataTransfer.TaskManagement.TaskManagementClientConsumer.GetMessages(Int32 messageCount)
   at Microsoft.DataProxy.MidgardCore.TaskManagement.HostTaskReceiver.<>c__DisplayClass16_0.<StartPullTaskHA>b__0()
Log ID: DispatcherRunLoopException

... followed by another similar error.

I have tried deleting the DB on the Azure side (I had truncated all tables with a hope to just bring in the data). I have also tried adding a new migration service to the integration runtime. Neither seem to have had any effect.

To add - the initial migration used the same data source, same machine to host the integration runtime on the same network. It worked fine.

Azure Database Migration service
0 comments
Answer accepted by question author
  1. Pratyush Vashistha 5,125 Reputation points Microsoft External Staff Moderator
    2025-10-08T10:01:42.15+00:00

    Hello TMADev,

    Thanks for reaching us out!

    This appears to be a version compatibility issue between your self-hosted integration runtime components and the Azure Data Studio migration extension. The System.MissingMethodException suggests that the runtime is trying to call a method that doesn't exist in the current version of the loaded assembly.

    Recommended Troubleshooting Steps

    1. Update Integration Runtime
    2. Download and install the latest version of the self-hosted integration runtime from the Azure portal
    3. Uninstall the current version completely before installing the new one
    4. Restart the integration runtime service after installation

    Clear Runtime Cache

    1. Stop the integration runtime service
    2. Navigate to the installation directory (typically C:\Program Files\Microsoft Integration Runtime)
    3. Clear the cache folder contents
    4. Restart the service

    Recreate Migration Service

    1. Delete the current migration service in Azure portal
    2. Create a new Azure Database Migration Service instance
    3. Generate new authentication keys
    4. Re-register your self-hosted integration runtime with the new service

    Verify Azure Data Studio Extension

    1. Update Azure Data Studio to the latest version
    2. Update the SQL Server Migration extension to the latest version
    3. Restart Azure Data Studio after updates

    To provide more targeted assistance, could you please share:

    1. What version of the self-hosted integration runtime are you currently running?
    2. When was the last successful migration completed, and have there been any updates since then?
    3. What version of Azure Data Studio and the migration extension are you using?
    4. Are you seeing any additional errors in the Windows Event Viewer under Applications and Services Logs > Microsoft Integration Runtime?
    5. What type of database are you migrating from (SQL Server version)?

    Additional Verification Steps

    1. Check that your integration runtime machine has stable internet connectivity to Azure services
    2. Verify that the service account running the integration runtime has proper permissions
    3. Ensure that no antivirus software is blocking the integration runtime processes
    4. Test the connection to both source and target databases from the integration runtime machine

    The authentication header provider error typically indicates a mismatch between the client-side components and the server-side expectations, which usually resolves with proper version alignment.

    Please try the update steps first and let us know the versions you're running so we can provide more specific guidance if the issue persists.

    Please "Accept as Answer" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.

    Thanks

    Pratyush

    User's image

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.