PDM, user cannot get any version or clear cache of certain checked out file

Hello all, We use PDM Pro 2023. A user in our Des Eng department informs me that he cannot get latest of an assembly that is checked out by another user.

Here’s the common settings I’m aware of: I’m probably missing some, will add as asked.

  • Always work with latest version is checked for the group
    • Enable get version from the SW PDM Add-in is checked
  • Des Eng group has permissions to view working versions

Things I’ve considered, tried, ruled out:

  • Restarted computer
  • Clear cache for that file, and the folder. That file is not cleared from cache.
  • confirmed no hidden ~$ lock file in folder for that file.
  • Confirmed no ghost SW process
  • Tried Get latest from Vault View, that file is grayed out in the ref file dialog, shows Checked out by another user warning.
  • Tried Get latest from SW PDM Add-in, same as vault view
  • Tried Get a version from SW PDM Add-in, same as vault view
    • Tried getting only rev stamped versions from add-in, same
  • Other users/PCs can cache and clear cache of this file.
  • Admin on that PC cannot get or clear cache of the file.

I’m 99% certain it’s an issue with that file on that local computer. But I don’t know what to check next. I’d rather not have to remove the vault view, delete the local files, recreate vault view. But I’m guessing that’s the solution?

Have not found this problem with any other files on that or other machines.

Brought up by more than one user in the Des Eng group is that when there’s a newish assembly in the vault that has been checked in and then checked out again, other users cannot get that assembly file if they’ve never cached it. Which seems wonky to me, I’ve never had that problem myself. Gut feel is it’s not related to the current problem, but it was mentioned.

Thanks for any suggestions.

We saw this a few weeks back. It was only some users, not all which seemed to me to be machine specific. There are no permissions that controls this that I’m aware of and the users are in the same group. Worked for some, but not for others. We didn’t find a solution and it got put on the back burner.

I need to revisit but in a big PDM to Windchill project. I thought maybe it had something to do with our new “super locked down” laptops. We can’t sneeze on it without authenticating and asking for permission to do anything.

1 Like

Thanks for the reply. Nice to know I’m not the only one with acknowledged gremlins slowly steeping on the back burner.
I too hope this is not from the security lockdowns that have been going around lately. Seems to be a trend.