Job Processor error with Vault 2025

Job Processor error with Vault 2025

kent.trigwell
Contributor Contributor
7,468 Views
47 Replies
Message 1 of 48

Job Processor error with Vault 2025

kent.trigwell
Contributor
Contributor

Hi all,

Since upgrading to 2025 Vault, we've been getting the error "An item with the same key has already been added." with PDF's being created in the job server que.

Not sure what's causing this issue.

Thanks!


[title modified by CGBenner 10/23/24]

0 Likes
7,469 Views
47 Replies
Replies (47)
Message 2 of 48

ihayesjr
Community Manager
Community Manager

Please create a support ticket for this issue.




Irvin Hayes Jr
Principal Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
0 Likes
Message 3 of 48

george_nevill
Participant
Participant

Have you made any head way with this?

I am now getting the same error as you have described.

Have created a ticket.

0 Likes
Message 4 of 48

BDCollett
Advisor
Advisor

I have seen this and could not find a reason either. Would be good to know the cause.

0 Likes
Message 5 of 48

kent.trigwell
Contributor
Contributor

Created a ticket, but they want a copy of our database, but it's quite large and it's not feasable to upload to autodesk. I'll wait to see if someone finds a solution.

0 Likes
Message 6 of 48

pbonenfant
Explorer
Explorer

We have the same problem

0 Likes
Message 7 of 48

cdbussey
Advocate
Advocate

In our testing, we have noticed a separate behavior based on the imported file. We have one Lifecycle transition (WIP to QA) that generates the dwf and pdf from an AutoCAD drawing. We have rules that places the file in the correct category based on the filename. Example, for our Structural Design Team, all filenames must start with "STR-DES". So a Structural Design file would be "STR-DES-BR549-00001.dwg". When the file comes into Vault with the correct prefix, when the transition occurs, the dwf and pdf are created without any issues or errors. BUT if someone loads a file (ex: "BR549.dwg"), and they manually sets the lifecycle & category, when the file transitions between the states, we almost always get an error. Not sure if this has anything to do with your error, but it would be interesting to know if you get a different results following the two processes.

0 Likes
Message 8 of 48

george_nevill
Participant
Participant
Interesting to see that you are getting this error with AutoCad drawings.

I have found that if I remove all of the model views from the drawing, I am then able to create PDFs fine. This suggests to me that the issue I have is with the referenced 3d model and not the drawing itself?

I managed to pack and go the drawing in question to send to Autodesk support, they were unable to recreate the problem though unfortunately. They have suggested a number of things to try but to no avail so far.
Message 9 of 48

cdbussey
Advocate
Advocate

I don't think it has anything to do with the drawing, the error message shows the job processor can't generate the pdf and them make it match the parent. Our visualization files are set to follow the parent.

 

Error message: An error occurred while attempting to synchronize states between the source and the PDF file: The specified lifecycle definition could not be found.; An error occurred while attempting to synchronize revisions between the source and the PDF file: Invalid Revision Definition change.

 

But, as I mentioned, if the original dwg follows the naming schema, there is no error. This certainly seems like a bug because not all files will follow a naming schema when added to Vault, and I've not had success building category rules using wildcards or other characters to cover for all naming possibilities.

0 Likes
Message 10 of 48

johan.degreef
Advisor
Advisor

Same here - 2025 - PDF creation tasks in Vault job processors give this error: "An item with the same key has already been added."

 

This article does not help:

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/An-item-with-the-s...

 

Anyone has other solutions?

Many Thanks, Johan

Inventor 2025, Vault Professional 2025, Autocad Plant 3D 2025
0 Likes
Message 11 of 48

ihayesjr
Community Manager
Community Manager

@kent.trigwell 

Did you provide any files that reproduces the problem in your support ticket?




Irvin Hayes Jr
Principal Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
0 Likes
Message 12 of 48

piotrbQKW4K
Participant
Participant

Try uninstalling Vault Client 2025.1 update. It worked for me.

Message 13 of 48

lojens
Contributor
Contributor

Hi

We had the same problem and it helped to uninstall 2025.1 update from the pc running as job processor.

Thanks

0 Likes
Message 14 of 48

johannes.bauer
Autodesk Support
Autodesk Support

Hi all, Could you please try installing inventor interop from Autodesk account? 

 

johannesbauer_1-1729751217708.png

 



HTH
-Johannes

Customer Technical Success
0 Likes
Message 15 of 48

george_nevill
Participant
Participant

Hi Johannes,

 

Installing interop did not make any difference for me.
Am still on 2025.1

 

Thanks,

George

0 Likes
Message 16 of 48

george_nevill
Participant
Participant

Uninstalling Vault 2025.1 update fixed the issue for me also.

Message 17 of 48

johan.degreef
Advisor
Advisor

@george_nevill wrote:

Uninstalling Vault 2025.1 update fixed the issue for me also.


+1

Inventor 2025, Vault Professional 2025, Autocad Plant 3D 2025
Message 18 of 48

ThomasRambach
Advisor
Advisor

Case ID: 23332233 submitted. Autodesk says no open cases were submitted for this.

Message 19 of 48

jaco011
Advocate
Advocate

Has someone found an solution? We have the same issue. Most PDF files are created fine. But some have the error 'An item with the same key has already been added.'
The model can't be (always) the issue, because the same model has multiple drawings. And for most files with this error the other drawings are created.

Message 20 of 48

joakim_edberg
Participant
Participant

Same issue here as well.. would be great if someone found a solution 🙂