Since this error looks pretty much like the one descibed by yours truly here, and since noone from Octopoos seem to care, maybe try my workaround. It's bizarre, but if it worked in my case...
Hi Olivier, I fixed the error like described by Olek. The error was on an upgraded site. I wont be able to reproduce ist since it was also just this one content type. thanks!