Hi, thanks for posting this. This happens with in place upgrade as well and the workaround suggested fixed the issue. But is this fixed now? can you please provide the support ticket reference.