Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
848 questions
How to fix Azure Migrate Appliance discovery source server validation error
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 84%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
Paul Mathews
0
Reputation points
I have setup Azure Migration appliance and I am getting the following code when I try to assess the source servers:
The server '192.168.20.10' returned an unexpected error. Error code: '-2146233086' Error details: 'Index was out of range. Must be non-negative and less than the size of the collection.Parameter name: index
I have validated that the credentials work as expected and also that WinRM connects between the servers, any help appreciated as I can find very little information on this error
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 32%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
Pavan Minukuri 1,025 Reputation points Microsoft Vendor2025-01-11T02:20:06.95+00:00 Hi Paul Mathews
Welcome to Microsoft Q&A, Thanks for asking question here!
Please try with these steps to resolve the error.
1.Make sure the Azure Migration appliance can connect to the source server at 192.168.20.10. You've already checked that WinRM is working, but it's a good idea to double-check for any network problems or firewall settings that might block the connection.
2.Confirm that WinRM is set up correctly on the source server. Ensure that the ports (5985 for HTTP and 5986 for HTTPS) are open and that the server is configured to allow remote management.
3.Even though you’ve verified the credentials, make sure they have the correct permissions to log in and perform the tasks needed by the Azure Migration appliance.
4.Check the Event Viewer on both the Azure Migration appliance and the source server for any errors or warnings that might give you more information about the issue.
5.Make sure your Azure Migration appliance is up-to-date. Updates can fix bugs and improve performance.
6.Sometimes, simply trying the discovery process again after making changes can fix the issue.
7.Look for any known issues related to this error code in Microsoft documentation or community forums. Similar errors have been reported when discovering physical servers or VMs on unsupported platforms.Reference link: https://learn.microsoft.com/en-us/azure/migrate/common-questions-appliancehttps://learn.microsoft.com/en-us/answers/tags/116/azure-migratehttps://learn.microsoft.com/en-us/azure/migrate/troubleshoot-general
Sign in to comment
Sign in to answer