ArgumentException: An entry with the same key already exists on loading MPP file (C# .NET)

Aspose.Tasks Product Family
1

Hello,

The attached file cannot be read by Aspose.Tasks library version 19.6.1.

The library throws the following exception:
https://drive.google.com/file/d/1wUcApTBdk5j21EJY7k75bov-NWgp0J03/view?usp=sharing

System.AggregateException: One or more errors occurred. —> System.ArgumentException: An entry with the same key already exists.

at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)

at System.Collections.Generic.SortedList`2.Add(TKey key, TValue value)

at #=z$X$jj1KCMVXAnGazGY305Hp3C6wFdCSDtfGT90M=.#=zS6Ll8TVF$$Vh()

at #=z$X$jj1KCMVXAnGazGY305Hp3C6wFdCSDtfGT90M=…ctor(Stream #=zGxUApnw2B5BE, Stream #=z_vJw56Y=, Stream #=zabr1ZvJrt9RB, Stream #=zlbOqZODpq3Wa, Int32 #=zRig4HIb$95Vw, Int32 #=zlNFYyGiHvz0r, Int32 #=zBU7mO7qt1mgO, Int32 #=z8BYR5ZBnDvqO, #=zhAMR1p4zICiHX4_c2LwTL9Uw4diwco3lyQ== #=z_cyF3mXfvaDy)

at #=z$X$jj1KCMVXAnGazGY305Hp3C6wFdCSDtfGT90M=…ctor(Stream #=zGxUApnw2B5BE, Stream #=z_vJw56Y=, Stream #=zabr1ZvJrt9RB, Stream #=zlbOqZODpq3Wa, Int32 #=zRig4HIb$95Vw, Int32 #=zlNFYyGiHvz0r, Int32 #=zBU7mO7qt1mgO, Int32 #=z8BYR5ZBnDvqO)

at #=zJBvy6MzkVyB4suhEb8blwxPlOcA6Yn3y$CsIqE0=.#=zGbU7M6ywbesE()

at #=zywKI5vRBCKyLt5gObB$LR9so$UIJJv81gjmco6I=.#=zGbU7M6ywbesE()

at #=znOQVByy$1XTCUA_Upag2m5IFxUZ$aUphSlAYkS4=.#=zSEs7SWt6bHpP()

at #=zpOW0J7ktCBieZgWgTqB_xxHKM7VuYzIBvw==.#=zrSPbSdw=()

at #=zpOW0J7ktCBieZgWgTqB_xxHKM7VuYzIBvw==.#=zrSPbSdw=(Project #=z$LIXDE0=, Stream #=z25WqQ4Y=)

at #=zvV1l5gk1IGc0AzaljdOf0h0=.#=zrSPbSdw=(Stream #=z25WqQ4Y=)

at Aspose.Tasks.Project.#=zQPHgVRanoqL$(Stream #=z25WqQ4Y=, ParseErrorCallback #=z4GW2$XeSYFUG, Encoding #=zq3NivIk=, PrimaveraXmlReadingOptions #=z5JFbYdY=)

at Aspose.Tasks.Project…ctor(Stream stream)

https://drive.google.com/file/d/1wUcApTBdk5j21EJY7k75bov-NWgp0J03/view?usp=sharing

2

@officetimeline,

I have observed the issue shared by you. An issue with ID TASKSNET-3319 has been created in our issue tracking system to further investigate and resolve the issue. This thread has been linked with the issue so that you may be notified once the issue will be fixed.

3

Thank you. Our customer reported that this issue started when they updated to the latest update for Project 2019. Not everyone has been issued that update because of how Microsoft rolls out updates and how companies apply them in their organizations. As Microsoft rolls out this update more broadly, we expect to see this issue become problematic for a lot of our customers using Project 2019.

4

@officetimeline,

Thanks for sharing information with us. We will share good news with you soon.

5

Thank you! We have some customers waiting for the fix so we’re hoping you guys can get to the bottom of it.

6

@officetimeline,

I have verified from our issue tracking system and like to inform that the concerned issue is likely to get resolved in upcoming Aspose.Tasks for .NET 19.7. We requires for your patience till the time the issue gets resolved.

7

Hi, can you please provide us with an approximate date for when .NET 19.7 will be released? We’d like to be able to communicate a timeframe to our customers.

8

@officetimeline,

The upcoming version is likely to be available during July 2019. We will share the good news with you as soon as the product will be shared online.

9

Thank you for your quick reply!

10

Hello, Microsoft has now rolled out the update to Office broadly and now our support volume has grown tremendously. Can you please provide us with a specific release date so we can notify our customers with some specifics on when their functionality will return?

Thanks,
Eddy

11

@officetimeline,

I have verified from our issue tracking system and like to share that the concerned issue has been marked as resolved in upcoming Aspose.Tasks for .NET 19.7, which will be released by end of July. We request for your patience till the the product is made available online.

12

The issues you have found earlier (filed as TASKSNET-3319) have been fixed in this update.

13

Thank you! Much appreciated.