Hi Planned a upgrade from 3.2.1m to 3.2.5e and got the same issue. Does anyone know if the 3.2.1m release is also affected ? solved the issue by ignore compatibility Check ;-) But it is a bit strange because that´s a supported upgrade path. Regards Markus
