by Anita Potgieter
It sometimes happens that for some or other reason a project schedule gets corrupted. One sign to look out for would include “failed and blocking correlation” messages (read my previous post to see “failed but not blocking correltation”), which basically means you’re publishing your schedule but something went seriously wrong and your data is not even synchronizing to the reporting db. Another sign would for instance be that you’ve changed/edited/added new custom fields and that it’s not showing in MSP even after you’ve cleared your cache.
One way I’ve found long time ago (when still working with EPM 2007), is to save that schedule as a .xml file. By saving as an .xml file you can also strip out local custom fields in the project schedule that causes problems when publishing these to the server.
How do you save as XML: In MSP 2010, go to File -> Save & Send -> Save Project as File -> Save As – > Select XML Format and save the file somewhere where you’ll preferably be able to find it:
Open the .xml file from MSP and Save and Publish back to the server.