mattwaddell

Also had the same issue, so I too disabled DB cache v0.6 and the error was gone.

Thanks for posting!