Unfortunately it'll be a bit of a painstaking process. which might lead you to the problematic data. You'd then need to start replacing the Powerproject generated content with MPXJ generated content element-by-element (or vice versa) until you trigger the failure when importing. The other way to tackle this would be to export your PP file from Powerproject as an MSPDI or PMXML file and compare the structure with what MPXJ produces. However, there are still other tools using it to exchange data and Project 2007 can open but not write. mpx format in favor of using xml as a standard exchange format. One way to address this might be to raise a support ticket with Elecosoft: they may be able to fix the issue on their end, or at least suggest what is causing the problem. At least a couple versions back, Microsoft started walking away from the. This appears to leave a log file in C:\Users\\AppData\Local\Temp which may shed some light on what it's having trouble with. The PMXML import seems to get a bit further than the MSPDI import, and fails when the new PP file is being written. You can see a minimal amount of failure logging in the Windows event log, but not enough to diagnose the issue. these are files which will happily import into Microsoft Project and P6 respectively, but cause failures when an import into Powerproject is attempted. A quick test suggests that indeed Powerproject doesn't like valid MSPDI and PMXML files generated by MPXJ from a Powerproject PP file.
