Problem adding library components to vault 2013

[rikard]

In 2011 and 2012 Vault Collaboration we used to have one category named "Standard" for Library and Content Center Files. The default state for the category is released.

When migrating to 2013 with the same rules and setting the engineering users can't add new CC parts to vault. When assembly files with new cc parts are checked in the system say:

                A problem occurred while attempting to add ........

                The server returned... : You do not have adequate permission to perform this operation.

The solution I found is to give permission to the engineer to have modify rights for Standard components or remove cc rules and manually change state to released. But it's not so safe and efficient as the previous workflow.

[mollons]

I have validated that I can check in files to the Vault and have them added to category which has a default released state via a rule.

Can you share your steps?

Have you applied the service pack to the client and the server?

[wseaston]

Scott,

Thanks for your reply.

I have created a "Is CC Part" property. There is a rule using this property to assign all CC Parts to a Content Center category. I have a Content Center lifecycle state which is assigned to my Content Ceter category with the default setting to set all CC Parts straight to released on check in.

I have noticed that this works fine if I check in projects (with CC parts) - It seems that it works fine as I am an administrator, however, if anyone from the "Draughtsman" group attempts to check in any CC part files we get the error mentioned earlier in the post.

I started going down the route of checking our secturity permissions for the CC lifecycle state but they are set to be the same as the administrator. I could not find anything in the vault settings which were different between the "Administrators" group and the "Draughtsman" group which would explain this behaviour and therefore assumed it was related to the bug mentioned in this post.

We installed the SP on both the Server and Client machines and are still having the same problem....

I really am not sure where I should be looking if it is a vault setting causing the issue.

Could you perhaps direct me if this is the case.

Regards,

Wayne

[wseaston]

Attached are some vault settings screenshots

[Kevin.Jaufmann-Ludwig]

Hi all,

just FYI: the reason for the behaviour was that draughtsman group didn´t have modify permissions on the library folder (folder security).

[wseaston]

See attached image for clarity.