This issue results from this issue: CDAT/cdms#334
One way to avoid this issue is to retrieve the file time units and if they are relative to the year 0 we could invoke cdscan with the flag: -e "time.units='days since 1900-01-01'"
We probably do not want to check the units on every file, but maybe could check units on files with particular error messages and rerun cdscan with the -e flag if they are tied to year zero.