FSA doesn't archive files with error "Not a valid Win32-FileTime"

Article:TECH188214

Created: 2012-05-07

Updated: 2012-05-14

Article URL http://www.symantec.com/docs/TECH188214

Article Type
Technical Solution

Product(s)

Show all

Languages

Show all

Problem

Enterprise Vault for File System Archiving (FSA) doesn't archive files with error "Not a valid Win32-FileTime" if the target file have time stamp of Jan. 01, 1601.

In addition, files within the same folder which doesn't have such old time stamp will be affected from the file and these files aren't also archived.

Error

Not a valid Win32-FileTime

Environment

Enterprise Vault for File System Archiving

Computer is in time zone rather than UTC (Universal Time Coordinated).

Cause

The oldest valid date/time for Win32 FileTime structure (Microsoft defined computer data type) is 00:00:01am Jan. 01,1601 in UTC (Universal Time Coordinated).

If the computer is in time zone rather than UTC (GMT), Enterprise Vault will calculate the file time stamp date/time +/- time-zone difference for internal processing purpose. For example, if the computer is in JST (Japan Standard Time = UTC - 9 hours), Enterprise Vault may calculate the time of the file time stamp date/time +/- 9 hours. So if the file's time stamp is within 9 hours from oldest valid date/time (aka. older than 09:00:00am Jan. 01, 1601 in UTC), the calculated date/time will be out from valid date/time range. This causes "Not a valid Win32-FileTime" error.

The improper error handle process causes the side effect reported in Problem section. (Files within the same folder will not be archived).

Solution

Workaround:

The time stamp of an old date/time (Year of 1601) must have been incorrectly set, and it is likely that the files have been imported from other platforms where extended attributes are supported. Symantec recommends to use a 3rd party tool to modify the file's date/time stamp accordingly, or to remove the affected files with the corrupt date/time stamp from the folder structure configured for archiving.

-------
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.

There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. However, the issue is currently scheduled to be addressed in the next major revision of the product. Please be sure to refer back to this document periodically as any changes to the status of the defect will be reflected here. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Symantec’s plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please see http://www.symantec.com/

Supplemental Materials

Source	ETrack
Value	2760197
Description	FSA doesn't archive files with error "Not a valid Win32-FileTime"

Source	ETrack
Value	2592079
Description	FSA - Archiving report log repeatedly returns 'Error Not a valid Win32-FileTime' & 'The value cannot be NULL'