'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix SharePoint Migration Agent Stopped Scanning After Folder Deletion
Question details
The user needs to restore the scanning process of the SharePoint Migration Agent after it unexpectedly halted due to the original source folder being deleted or relocated.
- Product
- SharePoint Migration Agent
- Device & OS
- not provided
- Scenario
- Migrating local files to Microsoft 365 when the source folder is deleted, causing the migration agent to stop scanning.
- Observed behavior
- The migration agent halts its scanning process and fails to proceed with the migration because the configured source path no longer exists.
Ensure you know the exact new directory path or replacement location of the deleted source folder before attempting to update your migration agent configuration.
Modify the Source Path in Migration Agent
Update the existing migration task with the new or corrected folder path to resume the scanning process.
If a source folder is accidentally deleted or intentionally moved during a migration setup, the agent loses track of the files. Updating the source path directly in the task settings is the quickest way to resolve this.
Open the SharePoint Migration Agent and locate the migration task that has stopped scanning. Select the specific source path that is causing the error.
Choose the 'Modify source path' option from the available actions for that task.
Type in or browse to the current, valid folder location that replaces the deleted directory.
Click on 'Scan content' to force the agent to re-evaluate the new folder and resume the process.
Delete and Recreate the Migration Path
If modifying the source path does not trigger a new scan, delete the stalled path and add it fresh.
Open a Microsoft 365 Support Request
If the scanning still refuses to resume, escalate the issue to Microsoft Support with the necessary diagnostic logs.
Looking for a Lightweight Office Alternative?
While managing complex Microsoft 365 migrations, you might want a fast, straightforward, and reliable office suite for daily document tasks. WPS Office offers excellent compatibility with Microsoft formats without the heavy resource usage.
- 1. Visit the WPS Office Website: Go to the official WPS Office website to find the latest free version.
- 2. Download the Installer: Click the download button corresponding to your operating system.
- 3. Install and Work: Run the installer and immediately start handling your Word, Excel, and PowerPoint documents with ease.
Frequently Asked Questions
Where can I find the SharePoint Migration Agent logs?
The migration agent logs are typically stored in the `%appdata%\Microsoft\MigrationAgent\Logs` folder on the computer where the agent is installed. You will need to compress these files into a zip archive when submitting a Microsoft support ticket.
Can I rename a source folder while the Migration Agent is scanning?
No, it is highly recommended not to rename, move, or delete source folders while a scan or migration is actively in progress. Doing so will invalidate the configured path and cause the agent to stop scanning.
Why does the 'Scan content' button remain inactive after updating the path?
The 'Scan content' button might remain inactive if the newly entered path is invalid, if the agent lacks the necessary file system permissions to access the new location, or if it has temporarily lost connection to the Microsoft 365 admin center.
