Comment 7 for bug 330272

The fact that two of you have started seeing this within the past few weeks would seem to indicate something changed in that time frame, or soon before. Did you all do an update around that time? What versions are you running? Have you run a database check? Do your error messages look very close to Kyle's (with the invalid looking date 222yyyy-22MM-22dd 22hh:22mm:22ss.22zzz)?

Thank you,

   Marc