Why can't you clear the local cache of a file that is checked out (per S-057467 in the knowledge base) by another user? Is there a good reason behind this?
I found in the "using a shared view with multiple Windows profiles" that your user privelages may be over restrictive. maybe?
Using a Shared Vault View with Multiple User Profiles
A user with local administrative Windows permissions creates a shared vault view. By
default, the user profile creating the view folder is granted full file permissions to any
files created or cached in that view.
Other Windows user profiles with more limited file access might not have sufficient
permissions to fully modify the locally cached files or to change the read-only flag, for
example, when checking out a file.
Ensure that all Windows user profiles that plan to use a view have appropriate file access
permissions for the folders and files in the view.
The following occurrences indicate that Windows permissions are overly restrictive:
• Checked-out files open in read-only mode.
• Newer versions of a file cannot be retrieved if an older version is already cached.
• Checked-in files remain writeable.
• Clearing a local cache fails.
Are you running into this issue?
I do not see where it says "another user"
The following rules are by design when it comes to clear local cache on a file in a vault view:
- You cannot clear local cache on a file that is checked out.
- You cannot clear local cache on a file that is checked in if one of its parent document is checked out.
E.g.: an assembly has a part reference, if the assembly file is checked out and the part is not, it will not be possible to clear local cache on the part file since it is being used by the checked out parent assembly.
- You cannot clear local cache if the local file is writeable (read-only flag is off).
- If SolidWorks toolbox is set up in the vault, the files under the toolbox folder will by default be excluded from clear local cache command.
Other possible reasons:
- The file you are trying to clear local cache for is held open by some other process, such as being open in an application. Use Process Explorer from Microsoft to find what process may have a handle to the file.
- The Windows profile which is currently logged in has insufficient permission modify or remove to the cached copy, thereby preventing Enterprise from removing the file when trying to clear local cache on the file. Refer to the installation guide, chapter "using a shared view with multiple Windows profiles".
I don't see "another user" either, but that is what I'm experiencing.
I have had some of my users experience files that were not being cleared and it was related to files they had ownership referencing other files.
One user was trying to clear part files but had onwership of an assembly that is referencing those parts. so it was not allowed.
Are you able to clear them from cache after the other user check them in?
That's it! My users didn't have full permissions to the vault. As soon as I granted them full permissions, they were able to clear the cache even if another user had the parent checked out. Thanks for the help Jason.
Retrieving data ...