Error "An Item with the same key has already been added"

[spascual]

Hi Sirs,

Any sugestion about this error.

VM210 SP1

Regards

[mollons]

Are the ipts (old and new) in the same file category in the Vault?

If one is assigned to a different category they could have different properties assigned to them.

I was only giving another data point, that at least one cause of this problem was solved in Vault 2011.

[spascual]

Yes, old an new IPT are in the same category. Now we are not using categories for files (default BASE).

[mollons]

The best thing would be to contact Product Support, as they can work with you much more closely to try to figure out the problem. They can do a web session with you to see your environment and have the necessary legal forms if you wish to send a dataset to us to investigate the issue further.

[spascual]

Thanks, I will try for twice.

Regards

[spascual]

Hi sirs, please,

We need to speak with an authentical product expert that knows exactly what is happenning when a file is assigned to an item.

Properties, web pages, registers,....

I think that in support can response to a common issues.

Thanks

[cmcconnell]

We saw this error on Vault Pro 2011 today FWIW...

[spascual · Accepted solution]

Hi sirs, support has worked

In my case, we have two custom properties that was making system runs bad.

One of them "GRUPO", an the other, the same but with blank space before it (human mistake) " GRUPO".

Although " GRUPO" is not active and mapped...???????

We have deleted it on the files affected and seems runs again well.

Thankyou very very much

Regards

[Anonymous]

I can report we have this issue today while using Vault Pro 2016 and Inventor 2016.

An article is published at Autodesk Knowledge Network

My vendor is contacted to get an update of the status.

[Anonymous]

Yesterday plotting was fine using batch plot, but today this issue has popped up and there has been little or no changes to the parts or drawings involved.  I know there is a workaround but workarounds are not fixes. 

I am using IV2019.4 with the latest Vault Server.

There must be an easy way of fixing the files.