Solved! Go to Solution.
Solved by Thomas Schwaiger. Go to Solution.
I was having this issue with an imported part as well. Turned out to be illegal characters in one of the custom parameters. When I removed those, it went right into vault.
@Thomas Schwaiger wrote:
Hello MzMeister,
please post the vlog file from when the error occured - they can be found on the server in C:\ProgramData\Autodesk\VaultServer\FileStore
Have a look at the iproperties of the file - specifically the assembly as it seems to be one causing the error. Watch out for special characters in both property name and value. You can also try to delete all custom properties to eliminate this option.
Error 1103 means "The child file specified for the association is still checked out". For this you should make sure to either Check in with Children or check in the children before hand.
Regards,
Thomas Schwaiger
Customer Success Engineer | Data Management | Autodesk
8 YEARS THIS HAS BEEN A KNOWN ISSUE! And it's still not fixed or caught correctly by Vault. Unbelievable. @broepke @olearya
Once the data is in Vault... it can't be checked out to fix it. Any files that use a file like this, if checked out, can't be checked in... So the ONLY way through the user interface that it can be fixed in 201 at least. Is to log in as the Admin and forcefully delete the file, then check in a new version without iProperties containing these special characters... which of course breaks a bunch of file references in the Vault. Not cool. I'm flabbergasted.
Scott Moyse
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Design & Manufacturing Technical Services Manager at Cadpro New Zealand
Co-founder of the Grumpy Sloth full aluminium billet mechanical keyboard project