Crash when trying to import Phoenix file from V5.6.3

Question

Crash when trying to import Phoenix file from V5.6.3

Closed this issue 7 months ago · 4 comments

I just downloaded the latest Phoenix version (5.6.3) and am having trouble opening some files I produced from it. All the sample files (compressed and not compressed) work fine, but the ones I generated do not.

A file is attached (zipped to be allowed)
Current Schedule.zip
and it gives me a System.NullReferenceException: 'Object reference not set to an instance of an object.' error. in String.cs because @this is null. Here is the stack trace.

Answer 1 · 2024-07-19T15:47:08.000Z

Hi, can you confirm which version of MPXJ you are working with?

Answer 2 · 2024-07-19T15:57:46.000Z

The latest 13.0.2 and my project is .NET 4.8. Jim

…

________________________________ From: Jon Iles ***@***.***> Sent: Friday, July 19, 2024 10:47 AM To: joniles/mpxj ***@***.***> Cc: James Pike ***@***.***>; Author ***@***.***> Subject: [External] Re: [joniles/mpxj] Crash when trying to import Phoenix file from V5.6.3 (Issue #718) Hi, can you confirm which version of MPXJ you are working with? — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/joniles/mpxj/issues/718*issuecomment-2239492535__;Iw!!Ofz1Xjg!6DzTUxUvXC_HT-6ltlAnmEJJRoNtEvA7LuELX4FoHu7-V9_-FC9x0hVf7emZnGd5qC9r64-KFhdPhbnWgL7mIHm3$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BCQ4MCUQOPKGFZH7NJZERBTZNEYJFAVCNFSM6AAAAABLEZXKCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZZGQ4TENJTGU__;!!Ofz1Xjg!6DzTUxUvXC_HT-6ltlAnmEJJRoNtEvA7LuELX4FoHu7-V9_-FC9x0hVf7emZnGd5qC9r64-KFhdPhbnWgJuxfNMO$>. You are receiving this because you authored the thread.Message ID: ***@***.***> This e-mail and any attachments are intended only for the named recipient(s) and may contain information that is legally privileged, confidential, or exempt from disclosure under applicable law. This message may be logged for archival purposes, may be reviewed by parties at Deltek<https://www.deltek.com/> other than those named in the message header, and may not necessarily constitute an official representation of Deltek<https://www.deltek.com/>. If you have received this message in error, or are not the named recipient(s), you may not retain copy or use this e-mail or any attachment for any purpose or disclose all or any part of the contents to any other person. Any such dissemination, distribution or copying of this e-mail or its attachments is strictly prohibited. Please immediately notify the sender and permanently delete this e-mail and any attachment from your computer. You are responsible for complying with all applicable data protection, import, re-import, export, and re-export control laws, including any applicable license requirements, and country-specific sanctions programs. Without limiting the foregoing, you are solely responsible for compliance related to the information you send, via email, to Deltek, its employees, or agents. Please contact ***@***.*** with any questions or concerns.

Answer 3 · 2024-07-19T16:11:47.000Z

Thank you! I had a quick look with the Java version which seemed to read the sample file OK, I'll create a test .NET 4.8 project to see if I can reproduce.

Answer 4 · 2024-07-22T12:00:53.000Z

I had a closer look at this and have found and fixed the issue. The underlying problem was that the activity total_cost and billed attributes, which I'd previously only seen with integer zero values (0), were represented as decimal zero values in your sample file (0.0000). The number parse error is what was triggering the null pointer exception, however this was being handled by JAXB (the XML binding library MPXJ uses) and was silently ignored. If you had ignored the exception being thrown within the library the file would have read ok.

I've updated Phoenix schemas to ensure that these monetary attributes are represented as double, which ensures that the relevant attributes are read correctly, and thus stops the exception from being raised. This change will be in the next MPXJ release.

This issue suggests that we may encounter other places where monetary values are not being read correctly, but I have yet to encounter any sample Phoenix projects which contain cost data. If I have a chance I will look at generating some...

In the meantime it's worth noting that JAXB has some version checking code which raises, and handles a null pointer exception, which you'll see at least once when MPXJ first reads an XML file. This can safely be ignored.