See Solution ID S-057321 in the SOLIDWORKS Knowledge Base.
This actually didn't work for us. We have also restarted the computers to no avail. I'm wondering if I'm missing some settings somewhere in EPDM to accomplish this automatically. This particular issue you pointed me to is for 2011 CAD Editor and reviewed on 2014. I currently have 2016 of CAD Editor. It doesn't seem to be corrected.
I also used the Process Explorer tool mentioned below. Nothing jumped out at me regarding the particular files/folders. I also don't know how to search for a particular file / folder in that software.
Below is S-057321 for everyone's reference.Solution Id:
SolidWorks Enterprise PDM 2011 CAD Editor
Technically Reviewed Date:
Question:What could be the reason for a grey "local" file or folder to remain in the SOLIDWORKS® Enterprise PDM local file vault view (cache) after renaming, moving or deleting the file or folder?
Answer:A grey folder indicates you are viewing a "local" copy of a folder that is found in the local vault view cache but not present in the file vault. Files that are only present in the local cache but not the vault also show up with a dimmed grey icon and their status column shows <Local FIle>.
- If the folder or file is moved, deleted, renamed on a different client, you may have a left over locally cached copy. See solution S-043537.
- If the currently logged in user lacks permission to see the folder/file, and a user with more permission previously cached it.
- If folder/file failed adding to the vault, or was added in offline mode.
- If user setting "Show only local files" is enabled.
What version of PDM are you using?
Are the files italicized while greyed out?
How is it that you are controlling the cache at log-in? of the vault
Solidworks EPDM version
Client Version: 16.03.0064
Build Number: 16.3 (B64)
Solidworks PDM Pro CAD Editor
Not italicized (see picture below, Hardware folder)
Per the Group settings - Cache Options - "Cache Options per Folder" tab I have both "Clear cache during log out" and "Refresh cache during log in". unchecked. There was an issue with this on previous versions as it was hanging up Solidworks and wouldn't let us progress.
Thanks for the reminder about this. I had SPR in with Solidworks on this issue and it was implemented for 2016 SP02 (below)
The following SPR (SolidWorks Performance Report) status has changed to Implemented.
SR# (Service Request): 1-8762144194
Description: Open or Save file in new SW session with Add-In enabled after you are already logged in to Explorer starts caching all 'Refresh cache on login' files
Version: 2016 SP02
I just checked "Refresh cache during log in". I logged out and logged back in and it got latest versions of several files, but the files / folders are still there in grey. That didn't seem to resolve this issue.
Perhaps, have the user who owns the folder RMB and Add to file vault.
All users are seeing the white folder?
Have you logged in to the vault from that machine using different users with different permissions? If there are any files in that folder or subfolders that are aren't accessible to the current user (but are accessible to another user) you will see the gray folders.
Our current setup for EPDM
1) Only Engineers have access to the Vault. Contributors and Viewers are not yet implemented.
2) Each engineer has their own computers, no sharing.
3) All engineers have the same permissions, except for the Admin, myself, also an engineer.
Scott, One engineer moved the files/folders and all other engineers see the grey folders. I don't want the other engineers to "Add to file vault" because it already exists in another location hence the first engineering moving it. (Reorganizing files/folders)
Jim, Per the setup above I have all engineers with the same permissions, except Admin, so only 1 person is logging in to see those files at each computer. When 1 engineer moves the files, all other engineers instantly see grey folders. I would just like EPDM to remove the folders instead of just turning them grey and leaving them.
Try Group Settings...Explorer....Automatically delete local read-only files that are not part of the vault
From the Help file:
Automatically delete local read-only files that are not part of the file vault Local folders and local read-only files that are stored only in the local vault view and are not part of the vault are automatically deleted.
SOLIDWORKS PDM uses a local cache mechanism; each vault view stores a cached copy of a retrieved file or folder.
For example, if a file or folder is deleted or moved in the vault from another client view, a cached local copy of the deleted file or folder is left in the local client views on other systems. This option ensures that these orphaned objects are cleaned up automatically
I did some testing with my test vault. If you create a local file in a folder on one machine, and then rename the folder on a different machine, the rename works, but the original machine will still show a gray folder. Only when you change the local file to read-only do the gray folder and the local file disappear. Renaming and moving of folders is prohibited if users on other machines have files in those folders that haven't been checked in (EPDM throws up an error in the Move dialog box).
In your original post you said that you don't want local files to be removed, just the gray folders. You can't have it both ways. If there is a local file in a folder and that folder is renamed from some other machine, the folder cannot be removed from the machine where the local file is located (unless that local file is read-only). And if the local file is read-only, it too will be removed.
Of course, if your users are creating lots of local files, they are probably doing something wrong. And just to be clear, I'm talking about truly local files: files that have not been added to the vault. Files that have been added to the vault, but have never been checked it are not local files. They are 'private state files' which are a different thing altogether.
I was hesitant to check this option because from everything I have read there are several ways to create <Local File>'s. I have a macro that creates PDFs and those are a <Local File>, but they are NOT Read-Only status. I have never thought to check that and this setting doesn't effect those files.
I checked the setting you mentioned and it removed all grey folders/files. There was 1 that was still lingering, but inside of it were grey files that were writeable. As soon as I changed those files to read-only, they were removed as well as their folders/subfolders. I don't know exactly how these happened, but this solves my issue.
Thank you for your help.