This is because with version 4.1 and higher the format of timestamp
changes to 0000-00-00 00:00:00. We had this problem, so we had to add a
few lines in the scripts that take this field and work with it