More details from another colleague:
The problem originates from the fact that DS-5 checks timestamps on files to determine if the PC clock has been set back.
A second issue is that on Windows7 (and Vista) setting the access time by the OS is disabled. Therefore a bad access time will be persistent over accesses. This must be enabled before we can change access times.
Check the setting with command "fsutil behavior query DisableLastAccess" and enable with "fsutil behavior query DisableLastAccess 0"
I found many files with an access time in 2017. The majority of the files were Acrobat and flash files (all Adobe). To fix the problem, the access time must be set back to today or earlier.
To reset the access time, windows users can download a tool to touch the files (Linux can just use touch).
Most windows touch tools cannot update read-only files. I found it easier to create a batch file to copy all affected files to a temporary directory. The copy operation will set the access time of the original file. After the copy, I delete the temporary directory.