Have you ever found a Solution for that Error ? I have the same after updated to 5.3 but i think thats not the Reason.