I get this error with every log file so the problem must be in the database somewhere and not in the logs that have been created since as these will all parse properly in a new installation.
I had this problem with version 3.05 too thats why i installed 3.06 hoping it would cure it but it only ...