Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MS Project exporting error #1390

Closed
markcwalton opened this issue Apr 4, 2017 · 5 comments
Closed

MS Project exporting error #1390

markcwalton opened this issue Apr 4, 2017 · 5 comments

Comments

@markcwalton
Copy link

Not sure if this is the same issue as previous poster.

Scenario: Schedule was originally created using MS Project 2016. I can Import the MPP into GanntProject without issue and modify it. I need to export to MPX format for import into Primavera SureTrak (for a client)

When I try to Export to MPX, I get the error:

--
Something went wrong
Export failure. Failed subtask: Export project

I'm attaching the Log file.

I also tried using MS Project 2016 to save the project to XML instead, but I can't Import it into GanntProject (myriad errors).

Thanks,

  • Mark

ganttprojectlog.txt

@dbarashev
Copy link
Contributor

Yes, it is the same issue and will be fixed in the next update. The workaround is to remove all useless custom columns named like "Number1", "Flag3", etc. Use context menu in the table header, "Manage Columns..."

@markcwalton
Copy link
Author

OK, I was hopeful but it did not work. I deleted every column except the first 14 (which you can't delete) and got the same error. Not sure if anything changed, but I'm attaching the pertinent log file.

I appreciate your help and quick response!
ganttproject.txt

@dbarashev dbarashev reopened this Apr 4, 2017
@dbarashev
Copy link
Contributor

dbarashev commented Apr 4, 2017

Can you try doing the same with resources?

Do not close this ticket please :)

@markcwalton
Copy link
Author

That did it! 👍 Did not think of that.

Thanks so much!

@jlruivo
Copy link

jlruivo commented May 6, 2017

I created an issue similar to this one (#1408). The work around also worked for me.
Shall I close it?
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants