Archiving Report log contains large number of entries with *** Error *** - Not a valid Win32-FileTime

Archiving Report log contains large number of entries with *** Error *** - Not a valid Win32-FileTime

Article: 100027222
Last Published: 2021-08-13
Ratings: 0 0
Product(s): Enterprise Vault

Problem

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.

Error Message

fileserver.domain.local\share\folder\subfolder\file.txt 4464 File-Servers 2Months-Policy All-Files ARCHIVE  *** Error *** - Not a valid Win32-FileTime.

  

Cause

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.

In the above error sample the mDate ( Modified Date or LastWriteTime) is shown as 01.01.1061
Windows explorer fails to render the information under Date modified column for files with such dates.

 

Solution

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.

 
A Power Shell  script has been provided to assist with the identification of the affected files.
 
Ideally the path to be used with the script should be at the highest level possible as some files reported with the error may not necessarily be affected by the unexpected date stamp.
 
On the file server, open Power Shell console running as Administrator and execute following command:
 
Where the path to the affected file is \\fileserver.domain.local\share\folder\subfolder\file.txt
 
 
dir " \\fileserver.domain.local\share\folder " -r |  sort LastWriteTime | Select-Object -first 5|ft –wrap fullname, lastwritetime
 
 
The above command will return the first 5 files where the LastWriteTime is the oldest, therefore the affected  file or files will be included. If more files are potentially affected the option –first 5 can be increased accordingly, i.e. –first 100
 
Once the files have been identified they can be either modified to reset the mDate or removed from the current location which would allow the Archiving Task to complete without errors.
 
 

 

References

Etrack : 2592079

Was this content helpful?