Forum Discussion
Storage Migration Service Inventory completed with errors
Hi, I am running Windows Server 2019 Storage Migration Service Server to migrate a Windows Server 2012 R2 Server to Windows Server 2019. The Job, on 3 of my most important shares, says Completed with...
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
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.
- A 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- I 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.
- I found that continuing on to transfer the files will give you good information for troubleshooting issues. You can run the transfer / sync multiple times.
- I 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.- SMS 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.
Well I'm about to throw in the towel. I started this huge 4TB 2008 R2 file server migration project about four weeks ago and I'm no further ahead.
- inventory scan fails on some files with vague error messages - checked rights and enabled log path names
- data transfer scan keeps getting stuck - doesn't timeout - spinning bagel for hours & hours - today it's stuck @ 44%
- hesitant to STOP the transfer as last time I did that it auto created a bunch of preexistingdata folders which ended up filling the destination volumes and the data transfer failing due to lack of space - i ended up restarting the entire process only to be stuck AGAIN
There is just no rhyme or reason why it keeps struggling. It worked great on my tiny test server so perhaps this server is just too big not to fail.
Not sure where to go from here.
