Yes we have seen this one before, take a look at the following thread forum thread:
where @DarkYamik found a work around. It seems there is possibly a regional issue with the date parser in some versions of an upstream package.
Let us know if this gets your sorted. We have had a few reports of this, some caught at the time and others not but as you see from that thread it works on some systems and not on others.