The support forum

Unable to sync following a restore

biship :

May 07, 2019

I lost a drive and after purchasing a new drive, used robocopy to copy back the files (at 2019.05.04 14:19:40.736)
Now, when running the backup, nearly all files fail:

2019.05.07 10:15:04.836 (UTC-5) 2 2         44266. Updating file MP3s\Roxette\Room Service\09 Try (Just A Little Bit Harder).mp3
2019.05.07 10:15:04.836 (UTC-5) 3 3             Details
2019.05.07 10:15:04.836 (UTC-5) 3 4                 Source: 4.98 MB, created 2019.05.04 14:19:40.736, modified 2014.04.20 11:45:27.000, archive
2019.05.07 10:15:04.836 (UTC-5) 3 5                     Raw: 5221103 / 132014675807367290 / 130424823270000000 / 00000020
2019.05.07 10:15:04.836 (UTC-5) 3 4                 Backup: 4.98 MB, created 2010.06.30 13:03:34.000, modified 2014.04.20 11:45:27.000, archive
2019.05.07 10:15:04.836 (UTC-5) 3 5                     Raw: 5221103 / 129223910140000000 / 130424823270000000 / 00000020
2019.05.07 10:15:04.978 (UTC-5) 0 3             MoveFileEx() failed with 801f0005
2019.05.07 10:15:04.978 (UTC-5) 3 4                 Context: \\?\UNC\basement\Backup\COMPUTER\D\MP3s\Roxette\Room Service\09 Try (Just A Little Bit Harder).mp3.bvckup \\?\UNC\basement\Backup\COMPUTER\D\MP3s\Roxette\Room Service\09 Try (Just A Little Bit Harder).mp3

Alex Pankratov :

May 07, 2019



No idea, sorry.

The error itself stands for "An invalid name request was made. The name requested cannot be retrieved at this time. ", but seeing how it comes from a remote machine, this may not be entirely accurate if that machine is not running native Windows.

Your best bet would probably be to look through the logs on \\basement box and see if there's anything on relevance.

biship :

May 07, 2019

There's nothing in the \\basement event logs. Both PC's are running Windows 10. The perms on the \\basement files are correct, but I can't even rename a file remotely. I get the same error in Explorer. I can create a new file in the folder. I guess there's a perms issue on the existing files. I'll try to reset/replace the perms.

Alex Pankratov :

May 08, 2019

It's a fair guess I think. The error happened when attempting to rename a newly created file (xyz.ext.bvckup) to its target file (xyz.ext) with the latter already existing. Meaning that creating files is OK, but there's something off with files already in place... though the error code itself is weird. I've never seen it before and I've seen my share of them.

New topic

Create
Made by Pipemetrics in Switzerland
Support

Updates
Blog / RSS
Follow Twitter
Reddit
Miscellanea Press kit
Testimonials
Company Imprint

Legal Terms
Privacy