Page 1 of 3

Important: Not a valid win32 FileTime

Posted: 15 Dec 2021, 19:03
by cobian
Are you one of those experimenting the Not a valid win32 FileTime error?

If so, I would need you to send me the list you are using AND the settings file . I would also like to know what the sources are: are they a network source, what file system is used, etc. You could also send me all the information generated by Tools-System information-Drives!

Thank you in advance.

Re: Important: Not a valid win32 FileTime

Posted: 17 Dec 2021, 09:57
by vgmcsd2
Hola. ya te he respondido por el otro hilo. Una vez haga las pruebas te comentaré algo. gracias

Re: Important: Not a valid win32 FileTime

Posted: 26 Dec 2021, 07:27
by gvd
Hello everybody,
cobian wrote: ↑15 Dec 2021, 19:03I would need you to send me the list you are using AND the settings file.
AFAIK, you should attach following files for Luis to understand what is going on :
  • Cobian Reflector tasks list : C:\Program Files\Cobian Reflector\Lists\MainList.lst
  • Cobian Reflector settings : C:\Program Files\Cobian Reflector\Settings\Cobian Reflector.ini

Re: Important: Not a valid win32 FileTime

Posted: 02 Jan 2022, 14:39
by MutatoNomine
I get the same message "Not a valid Win32 FileTime" and the backup stops at that point. I as not able to isolate the offending file. I could not drop the MainList.lst file into the the message box, getting the error "Invalid file extension", so I zipped both files (the .lst and the .ini files). Please help if you can.

Re: Important: Not a valid win32 FileTime

Posted: 02 Jan 2022, 15:25
by cobian
OK. it would be great if you would like to set an end to this. Any user reporting this just lets seems to give up directly.

It seems to me that the problem may lay on the DLINK side.

If you create a directory that is not on the root Volume_1,

for example \\DLINK-34025\Volume_1\Test and set this as a destination, do you still get the same error?

Re: Important: Not a valid win32 FileTime

Posted: 04 Jan 2022, 07:41
by MutatoNomine
Did not get same error - only backed up a small directory; did you need me to do a full backup? New .lst and .ini files attached, together with screen shots of the manual creation of destination directory and log. New .ini file was created (uiUser.ini). Am happy to try more options if it helps.

Re: Important: Not a valid win32 FileTime

Posted: 05 Jan 2022, 22:53
by cobian
So it seems like it's the "root" directory giving problems. If you check the properties for \\DLINK-34025\Volume_1 what do you see there? What timestamps are found?

Is this a directory that you have created and shared yourself or is this an "out of the box" directory by DLINK?

Re: Important: Not a valid win32 FileTime

Posted: 21 Jan 2022, 15:35
by immto
I'm also getting the error on one of my backups.

Both drives are local on this machine, but the data on this backups source drive is coming from a network location.

Both local drives have a NTFS files system. source drive is a 10TB Sata drive. Destination drive is a 2TB RDX.

Files are attached.
Desktop.zip
Zip includes the list and settings files.
(7.05 KiB) Downloaded 121 times

Re: Important: Not a valid win32 FileTime

Posted: 21 Jan 2022, 15:59
by cobian
I would like to reproduce this, but every single time anyone reports this problem, they leave the thread. I hope this is not the case again.

So:

Source: local drive (not network), NTFS
Destination: local drive (not network), NTFS

Do ALL tasks report the error or it's only task 2 (RDX-VISUAL) as I guess?

Re: Important: Not a valid win32 FileTime

Posted: 21 Jan 2022, 16:11
by immto
The task with the error was the aisql1 actually. The others completed without error.