Hi.
I'm getting Windows Error 87 when trying to sync files that have no
modification date. (Those sometimes show up as 1970-something and sometimes
the date is just empty) Those files are rare and I don't know how to create
them. If it helps, I could send one of them. For more information I need to
get back to my work computer.
Windows XP
FFS version unknown (d/l 2-3 months ago)
Error 87 on files with no modified date
- Posts: 14
- Joined: 14 Sep 2012
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
I fear if you just send them, the metadata will become lost. Instead can you
make a screenshot of all file times (create, access, modtime) by right-
clicking the file, then go on properties?
Additionally can you post the full error message? I'll want to know where
exactly the copy operation failed.
make a screenshot of all file times (create, access, modtime) by right-
clicking the file, then go on properties?
Additionally can you post the full error message? I'll want to know where
exactly the copy operation failed.
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
Also: what are the source and target file systems? Windows Error 87 is
"invalid parameter", this is likely to one of the file systems not supporting
the modification time given.
"invalid parameter", this is likely to one of the file systems not supporting
the modification time given.
- Posts: 14
- Joined: 14 Sep 2012
Source is NTFS, destination is FAT32.
AFAIR this error occurs every time but the first time syncing. I suspect FFS
detecting an identical file in both locations with different timestamps. When
it tries to copy timestamps from one file to this other, this procedure fails.
I will send you screenshots ASAP.
AFAIR this error occurs every time but the first time syncing. I suspect FFS
detecting an identical file in both locations with different timestamps. When
it tries to copy timestamps from one file to this other, this procedure fails.
I will send you screenshots ASAP.
- Posts: 6
- Joined: 17 Sep 2012
I get this error too. . Source NTFS, dest. FAT32. I have an photo cataloging
program that allows me to set the logical photo date < 1970, but which also
gets propagated to the file modified date. I have to use a "touch" style
program to then set the file modified date > 1970 to work around the error 87
problem.
program that allows me to set the logical photo date < 1970, but which also
gets propagated to the file modified date. I have to use a "touch" style
program to then set the file modified date > 1970 to work around the error 87
problem.
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
The problem is explained with the limitations that apply to FAT32. FAT
supports date ranges from 1980 to 2107, while NTFS already starts at year
1601. The usual behavior of FAT drives is to respond with
ERROR_INVALID_PARAMETER (87) upon request to set an unsupported date. This is
a FAT limitation, but there is still something I can do:
I've made the error message more self-explanatory:
[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_5.8_beta_setup.exe]
supports date ranges from 1980 to 2107, while NTFS already starts at year
1601. The usual behavior of FAT drives is to respond with
ERROR_INVALID_PARAMETER (87) upon request to set an unsupported date. This is
a FAT limitation, but there is still something I can do:
I've made the error message more self-explanatory:
[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_5.8_beta_setup.exe]
