In our previous blog post we covered an overview of what migration endpoints are, how to find them and what makes them tick. In this post, we will cover related troubleshooting. Note that this post h...
Updated Mar 30, 2020
Version 5.0
Blog Post
Mirela_Buru
Microsoft
MicrosoftMike Crowley , 401 is typically pre-authentication or bad credentials. If it happens intermittently, could be the credentials which expired or the admin account getting locked out. Would need to check IIS logs (the entries with 401) + FREB logs (for 401 status code) when this happens. You have FailureTimestamp and FailureType on the Get-MoveRequestStatistics, if you are able to start the move but it fails at some point with 401 Unauthorized.
You mentioned some complete, some don't. Look for differences: are those batches using the same SourceEndpoint? does Test-MigrationServerAvailability -Endpoint "" work when 401 is given in the migration batch? Or maybe the functional ones were created directly with new-moverequest from powershell, without using a batch/endpoint and different migration admin credentials.
You can open a support case with us and provide here the case number when you have a repro.