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.
Important: Not a valid win32 FileTime
Important: Not a valid win32 FileTime
--
Luis Cobian
Cobian Backup's creator
Luis Cobian
Cobian Backup's creator
Re: Important: Not a valid win32 FileTime
Hola. ya te he respondido por el otro hilo. Una vez haga las pruebas te comentaré algo. gracias
Last edited by vgmcsd2 on 17 Dec 2021, 10:00, edited 1 time in total.
Re: Important: Not a valid win32 FileTime
Hello everybody,
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
Gabriel
-
- Posts: 4
- Joined: 02 Jan 2022, 14:24
Re: Important: Not a valid win32 FileTime
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.
- Attachments
-
- Cobian Reflector.zip
- (2 KiB) Downloaded 129 times
-
- MainList.zip
- (2.77 KiB) Downloaded 134 times
Re: Important: Not a valid win32 FileTime
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?
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?
--
Luis Cobian
Cobian Backup's creator
Luis Cobian
Cobian Backup's creator
-
- Posts: 4
- Joined: 02 Jan 2022, 14:24
Re: Important: Not a valid win32 FileTime
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.
- Attachments
-
- mini_backup.JPG (108.62 KiB) Viewed 3265 times
-
- Setup_dir.JPG (88.15 KiB) Viewed 3265 times
-
- MainList (2).zip
- (3.65 KiB) Downloaded 139 times
-
- CR_uiUsers.zip
- (2.3 KiB) Downloaded 124 times
Re: Important: Not a valid win32 FileTime
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?
Is this a directory that you have created and shared yourself or is this an "out of the box" directory by DLINK?
--
Luis Cobian
Cobian Backup's creator
Luis Cobian
Cobian Backup's creator
Re: Important: Not a valid win32 FileTime
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.
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.
Re: Important: Not a valid win32 FileTime
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?
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?
--
Luis Cobian
Cobian Backup's creator
Luis Cobian
Cobian Backup's creator
Re: Important: Not a valid win32 FileTime
The task with the error was the aisql1 actually. The others completed without error.
Last edited by immto on 21 Jan 2022, 16:15, edited 1 time in total.