Copy Design - "You do not have adequate permissions to perform this operation"

[Fazlur_Rahaman]

I randomly get this error when I do the 'Copy Design' operation. Im confuse as to what is causing this error. It works on the same parts and randomly get this error on other even when the parts are the exact same thing and designed/modelled and uploaded to the Vault the exact way. 

I also noticed Autodesk put a workaround to this problem, I'm more confused about the 'Workaround' they have posted. They suggest restoring the Registry or enabling Prompts.  I failed to understand how any of these solve the issue here 

Here is the link to their post: https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Error-You-do-not-h...

If anyone encounters this, I would like to know what you have done to solve this. Have you followed the Autodesk Wrokaround and what was the outcome? 

[ihayesjr]

I believe the workaround in that article was because of an older version that no longer applies.

This error will indicate that you don't have the correct permissions to do a step post the copy. Usually, this step involves updating properties on the file being copied.

After the file is copied, what permissions do you have on the new parts, in your example?

[Fazlur_Rahaman]

Hi @ihayesjr ,

I have the same permission as I did on the source file. 
As you can see on the list, Item 3 is missing. That is because Item 3 was copied as expected, but the other 4 gave the error. All five parts were designed and uploaded to the vault using the exact same process and permission. I am puzzled as to why Item 3 worked but not the other ones. 

[ihayesjr]

Does it work if you try to copy only one of these that failed?

Are you copying all of them into the same folder?

[Fazlur_Rahaman]

I did some testing and found that if I Copy-Design at the individual level, it works as expected. However, I get the error if I do it at the assembly level where these parts are together. 

[Fazlur_Rahaman]

Update to the previous comment, the Copy-Design worked with Item 1, but failed on Item 4 at the Part level. 

[ihayesjr]

What version of Vault are you using? Are you up to date with the latest updates?

[Fazlur_Rahaman]

@ihayesjr 

Currently using 2019, will be upgrading to 2022 in a month or so. I do have the latest updates installed. 

[Gabriel_Watson]

Hey Fazlur,
In my notes it seems I have encountered this and used Workaround #2. It is not actually a workaround, but possibly this allows for the user's Vault Client to update any Items associated with the files. Part "-04" seems to be your problem one and I would guess it is perhaps "tangled" with an Item that copy design needs to touch while doing this operation (bad programming?). I like to think of Vault file and object relationships as a spider's web, and it requires touching a lot of strings to update and some copy content glued to it.

Anyhow, another way to get a similar error is by throwing a Vault search for All entities instead of just files, when the user has no Role assigned to see/search Change Order entities. So, I would bet this is on the permissions/roles side of things. If possible, I think it would make sense to share what your user permissions are, whether you have tested copying this as administrator, and if there are items associated with those files.

P.S.: the knowledgebase article seems so badly written, but I would guess the registry alteration is just to "reset" the Inventor User Profile in case it is corrupted, while the prompt value alteration is a hail-mary in case there was a prompt thrown during the copy design (I'd say not even worth testing, but it's harmless).

[Fazlur_Rahaman]

Hi @Gabriel_Watson ,

We don't use Item, so the files are not tied to it. The puzzling part for me is that all of these are modelled same time and put on an assembly and uploaded to Vault together. So to have one work and rest didn't is what I don't understand. This happens randomly. I have noticed this happens to other parts too, not just these ones. 

We don't use EPR Manager role or Item Editor Level in our Vault. And we don't want to disable the BOM update as that is one of the main reasons we use the Copy-Design.