Forum Discussion
Storage Migration Service Inventory completed with errors
Hi. In the Transfer Details section for each server (a pull up from the bottom of the WAC screen), there is an option to save the Error log (as CSV) then open in Excel and look at the per-file errors. The codes will all be Windows Error codes as documented here:
https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes
If still not able to determine why certain files aren't transfering, let me know (I reserve the right to send you to MS Support for specific troubleshooting, naturally 😀).
Ned Pyle | Principal Program Manager, MS | @nerdpyle on twitter
Hi, I'm trying to troubleshoot the "couldn't inventory some devices" during the "scan" phase of the storage migration.
I realize that it may be choking on long file names and 0kb files but how do you access this CSV?
I don't see it anywhere in the WaC console.
Thanks
- NedPyleMay 20, 2021Former Employee
Thom Edwards Hi. There is no CSV for Inventory, only for Transfer. If you are seeing an inventory failure the details are in the SMS event logs.
- earbangDec 23, 2022Copper ContributorA related question. We're seeing five file failures out of nearly 4million files. The SMS proxy log appears to have one record for each file inventoried. Does it also enter a record for the failed files? I'm wondering what the syntax is for failed files, that would be useful to know in sorting through so many records. Success records say:
12/21/2022-10:04:20.683 [Verb] Endpoint scan on endpoint ShareName found file- nufanFeb 17, 2023Copper ContributorI have the same issue, was able to find errors in the proxy logs for failed FOLDERS and corrected all those. Unfortunately I have 2 failed FILES now and can't find any errors in the SMS Logs for those.
- Thom EdwardsMay 23, 2021Copper ContributorI found some bunk rights but what to do about the insanely long path names? I tried the registry key on the WAC server but the shares still fail to inventory for this reason.
Thanks so much.- NedPyleMay 24, 2021Former EmployeeSMS supports long path names, as long as NTFS allows, you don't need to make registry changes. If it's failing there you need to open a support case, that's not supposed to be happening.