Copy Design Error

[kristin93g]

Hi all,

I've been getting this "Value cannot be null, parameter name: Path2" error when using copy design on certain assemblies in vault.
I know this has something to do with a lost connection with an imported component.
However I'm working in assemblies with sublayouts and many many components so it is very hard to try and find the broken link.

Is there any workaround to get rid of this error, if I don't care about the broken reference?
Or at least to show the broken reference so it is easier to find from top level?

[CGBenner]

@kristin93g 

Did you ever find a solution to this issue?  I wonder if you would have more luck in the Vault forum?

[kristin93g]

Hi, 

No I haven't got any answers but I also put in a Support Case for this and somebody is looking into it at the moment. 

Perhaps the Vault forum has more answers though.

[Gabriel_Watson]

Try through iLogic:
https://forums.autodesk.com/t5/inventor-ilogic-and-vb-net-forum/how-to-tell-if-an-assembly-is-missin...

[ihayesjr]

In order for Copy Design to work properly, you need to resolve the broken links or remove the links using what @Gabriel_Watson posted above.

[kristin93g]

Thank you for your answer.

I tried the ilogic codes and they found no unresolved issues in my assembly, but I still can't do a copy design.

Previously we had 2019 version which was not sensitive to broken links in copy design so a lot of our larger projects pre update are now with this problem. 
Often we also have subassemblies so to resolve the link we would need to fix it in the source and save and check in all assemblies up to top level. So if it is at all possible to bypass this error that would be a good fix for me as well

[ihayesjr]

@kristin93g 

Have you looked at this?

"Value cannot be null. Parameter name: path2" during Vault Copy Design | Vault Products | Autodesk K...

[kristin93g]

Yes, I tried this method. It worked in one assembly but in others I've found no broken links or substitutes and then others that have 200 components and some in subassemblies it is very hard to find what isn't working