Error 1455

[avaya2012]

I recently checked a couple small assemblies into Vault from Inventor 2013 from one computer then came to mine and checked it out to do my thing.  I then created a drawing and checked both back into Vault.  Everything seemed to be working fine until I tried to Assign Item to the assembly in Vault.  I get Error 1455 which reads:  The file was added in a way that did not include the correct item data. 

What did I do wrong?

What can I do to fix this issue?

Thanks

[avaya2012]

I recently checked a couple small assemblies into Vault from Inventor 2013 from one computer then came to mine and checked it out to do my thing.  I then created a drawing and checked both back into Vault.  Everything seemed to be working fine until I tried to Assign Item to the assembly in Vault.  I get Error 1455 which reads:  The file was added in a way that did not include the correct item data. 

What did I do wrong?

What can I do to fix this issue?

Thanks

[gavbath]

This helped me thanks. I was performing a check-in through the API, and had the option to upload BOM data set to false, which was causing this error. Your comment helped me to figure that out, so thanks.

[gavbath]

This helped me thanks. I was performing a check-in through the API, and had the option to upload BOM data set to false, which was causing this error. Your comment helped me to figure that out, so thanks.

[Anonymous]

Glad I could help.

Cheers

Kevin Tucker

Section Head (Drawing Office)
Engineering Department
Welfit Oddy

Work: +27 041 4046715
Cell: +27 0829409891
Fax: +27 0865284776
Email: ktucker@oddy.co.za

[Anonymous]

Glad I could help.

Cheers

Kevin Tucker

Section Head (Drawing Office)
Engineering Department
Welfit Oddy

Work: +27 041 4046715
Cell: +27 0829409891
Fax: +27 0865284776
Email: ktucker@oddy.co.za

[Anonymous]

I have typically been able to overcome this error by removing the offending file from the item and adding it back to the same item.

To do this, you edit the item, right-click on a file, first choose Go to Folder (this happens in the background), right-click again and select Remove Link, Save & Close the Item.  The folder you brought up before will be the active window.  You can select the file you just removed from the item and pick Assign Item again.  Click next on the first screen, and right-click in the Replace With column.  Click Select Replacement Item and choose (check) the item originally assigned.  Once it is back in the Item, you can verify the success by running Update 

Sometimes, the most difficult part is finding which file is the problem.  It would be nice if the error specified which "file was added in a way...".

[Anonymous]

I have typically been able to overcome this error by removing the offending file from the item and adding it back to the same item.

To do this, you edit the item, right-click on a file, first choose Go to Folder (this happens in the background), right-click again and select Remove Link, Save & Close the Item.  The folder you brought up before will be the active window.  You can select the file you just removed from the item and pick Assign Item again.  Click next on the first screen, and right-click in the Replace With column.  Click Select Replacement Item and choose (check) the item originally assigned.  Once it is back in the Item, you can verify the success by running Update 

Sometimes, the most difficult part is finding which file is the problem.  It would be nice if the error specified which "file was added in a way...".

[john_j_garcia]

If anyone happens to still have this issue too, I had this one for quite some time and after a lot of time spent on it, it is 100% files checked out below the item in question.  The easiest way to fix is to look in the uses tab, add column "checked in" expand all, and review the entire list (unfortunately).  Files that are checked out have a blank date field.

[john_j_garcia]

If anyone happens to still have this issue too, I had this one for quite some time and after a lot of time spent on it, it is 100% files checked out below the item in question.  The easiest way to fix is to look in the uses tab, add column "checked in" expand all, and review the entire list (unfortunately).  Files that are checked out have a blank date field.

[Toon.Broothaerts]

Experienced this in Vault Professional 2021.

User wanted to perform "Assign/Update Item" on a complex Inventor Assembly for initial release and got this error.

This IAM contained multiple parts, of which some were designed before Vault was introduced in our company. It is suspected that something went wrong during migration of one or more of the IPTs used in the IAM, resulting in a "NaN" value in the Density -iProperty of some IPT.

We fixed this by:

1. Check out the IAM and all of it's children
2. In the Manage -tab, hit Rebuild All
3. Try to check-in the IAM and all of it's children
4. If you get errors during this procedure: go to the faulty files and check its iProperties for "NaN" values where Vault might expect integers
5. Try to check in all the child-files
6. This should solve the issue.

(Admin rights might be useful to perform these steps)

[Toon.Broothaerts]

Experienced this in Vault Professional 2021.

User wanted to perform "Assign/Update Item" on a complex Inventor Assembly for initial release and got this error.

This IAM contained multiple parts, of which some were designed before Vault was introduced in our company. It is suspected that something went wrong during migration of one or more of the IPTs used in the IAM, resulting in a "NaN" value in the Density -iProperty of some IPT.

We fixed this by:

1. Check out the IAM and all of it's children
2. In the Manage -tab, hit Rebuild All
3. Try to check-in the IAM and all of it's children
4. If you get errors during this procedure: go to the faulty files and check its iProperties for "NaN" values where Vault might expect integers
5. Try to check in all the child-files
6. This should solve the issue.

(Admin rights might be useful to perform these steps)

[ThomasRambach]

Vault Professional 2023, 12 years later still has this same reoccurring error.

[ThomasRambach]

Vault Professional 2023, 12 years later still has this same reoccurring error.