Archiving Report log contains large number of entries with *** Error *** - Not a valid Win32-FileTime
If a file has an invalid Date/Time stamp, EV cannot process the file metadata information and fails to archive the items. Once this condition occurs, files under the same path will also be reported with the same error, even if the Date/Time stamps are valid.
fileserver.domain.local\share\folder\subfolder\file.txt 4464 File-Servers 2Months-Policy All-Files ARCHIVE *** Error *** - Not a valid Win32-FileTime.
While the actual cause for such unexpected Date/Time stamps is unknown, it is suspected that content from other platforms which may have been copied to Windows file servers, may have had the Date/Time stamps converted incorrectly.
As the unexpected date stamp corresponds to mDate, opening and modifying the file even by adding a space or a single character, saving and then removing the characters would be sufficient to reset the mDate with a valid stamp. Where this workaround may not be acceptable, the affected file can be moved to a different location which is not configured for archiving.
\\fileserver.domain.local\share\folder" -r | sort LastWriteTime | Select-Object -first 5|ft –wrap fullname, lastwritetime
Related Knowledge Base Articles
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):