Comment 9 for bug 1424855

Stanislaw,

Dave clarified in a support request that the error is observed in new 6.0 deployment (that is deployed from scratch) as well
So, it seems upgrade from 5.1 isn't the reason