The SharePoint Migration Agent was working normally until today, but it is now stuck in the "Cannot Scan" state. I cannot add new source paths or scan any existing ones. I already completely uninstalled the agent, removed it from the migration administration center, and reinstalled it, but the problem remains. Has anyone encountered this issue or found a workaround?
3 Answers
I’m seeing the same behavior. Migration tasks can still be created, but adding a source path or starting a scan does nothing. It worked recently and then suddenly stopped, so this may be a service-side problem rather than an issue with the local agent.
The service health information I checked did not show anything related to this, but the symptoms look like a broader outage. Reinstalling the agent probably won’t help if the migration service is failing to process scan requests. I’d wait for the backend issue to be acknowledged and keep an eye on the service status.
For larger on-premises migrations, I’ve found the Microsoft migration agent can be unreliable. It may be worth evaluating another migration tool if this becomes a recurring issue, although the agent can work successfully for many migrations when the service is operating normally.
I’ve completed hundreds of migrations with it without problems until now. I’m mainly looking for a practical workaround while figuring out whether this is a temporary service issue.