Share via

Microsoft Project 2016 XML Export Issue

Anonymous
2018-07-26T18:00:56+00:00

When saving two particular MS Project 2016 schedule as XML files , the export fails, with only the message "Microsoft Project has stopped working."  The other dozen schedules being saved as XML are saved without issue.

These are small project files, only start, finish, predecessor/successor links.  No other data, such as EVMS data.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

John Project 49,710 Reputation points Volunteer Moderator
2018-07-26T19:42:28+00:00

JPBehr,

It's possible the one file is corrupt. I'm assuming these files are not part of a linked structure (i.e. master/subprojects).

Normally saving to XML and then re-opening the XML file in Project is a way to clear corruption but it doesn't always work. If you are still able to open the file in Project, you could try methods 1 and 3 in the following Wiki article:

https://social.technet.microsoft.com/wiki/contents/articles/32054.ms-project-clearing-file-corruption-andor-bloat.aspx

Hope this helps.

John

Was this answer helpful?

2 people found this answer helpful.
0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-07-26T20:04:08+00:00

    John -

    You ARE the man of day. Thanks for the very quick response.  Yes, these are not sub-projects.

    -> Method 3 worked for me.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. John Project 49,710 Reputation points Volunteer Moderator
    2018-07-26T21:01:10+00:00

    JPBehr,

    You're more than welcome and thanks for the feedback.

    John

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more