Hi, we had a similiar problem when we upgraded from 4.6 to 4.10. Our solution was to upgrade directly to 5.0.
Regards, Holger
Hi, we had a similiar problem when we upgraded from 4.6 to 4.10. Our solution was to upgrade directly to 5.0.
Regards, Holger