Cannot "Get Latest Version" of a file when the file is checked out by another user, I have tried with user rights and with admin rights and neither seem to work.
Is this normal? I'm sure that we were able to do so previously.
Any help is appreciated.
Forgot to attach the image....
The two that I see that someone has checked out you already have the latest version as much as is possible. The part file you have 3/3 so your local copy is the latest. The assy you probably have 3/3 but what it's telling you is that it has been modified. You can only get latest version of what's on the server and you have that. If someone has it checked out then they may have updated it but you can't get it until they check it in.
WT
(**EDIT - see my reply below - this one is not correct.)
Are you on the same computer and using the same local view as the user that has the file checked out? That is the only thing I can think of that would prevent you from getting the latest version of a file that is in the vault and checked out by another user.
I am not on the same computer from which the file has been checked out.
Wayne,
Does the "-" on the "-/3" mean that it is being modified?
Since the part further in the tree is listed as "3/3" that means it is not being edited?
I must say that I apologize because I believe my previous reply was not correct.
The 3/3 means that there are 3 versions of that file and you have version #3, therefore the latest. I was thinking of the condition when you check out the file and then your local version shows the - as soon as you modify it.
I did some testing here and I believe in the condition you showed, the - means that you don't have any local copy and therefore should be able to get the latest version. So with that in mind, we suspect that one of the 28 warnings might be a fatal one. I could not replicate your issue - I was always able to get a local copy of the assy. And even when I had the latest but told it to get it anyway, I was able to check the box and it either went through the motions or just ignored me - either way I had the latest.
WT
Matt, the first number is the version you have in your local view and the second number is highest vaulted number. So for example a 2/3 would mean that you have version 2 in your local view and the highest version in the vault is 3. So in this case a get latest version would replace the version 2 in your local view with version 3.
A - (dash) in the place of the first number indicates that the file in your local view has been modified. There is no version in the vault that matches what you have in your local view.
I like WT, the other Wayne, cannot duplicate the issue here where I cannot get a file like your assembly that shows -/3.
WM
You know, what about that assy file being writable and changed? Shouldn't be, but it happens. But then there should still be the opportunity to check the box to check it out and it should pop up a warning such to tell you that the file is writable - do you want to fix it?
WT
Sorry for taking so long to reply. Yesterday I could not login to here to reply.
Matt, did you have the assembly file open when you brought up this Get dialog box? That could possibly explain not being able to get version 3 of the assembly listed as -/3. The part file listed as 3/3 is not "Getable" because you already have the latest version.
I have seen a similar problem.
All the user had to do was to keep the file checked out while cheking in. The result was that everyone else could not get the latest version of the file until the user checked in the file again or did an "undo check out".
This problem have now been fixed.
Was there ever any resolution to this? We are seeing the same issue. We have some users who can get latest version when a file is checked out by another user and some who cannot. All permissions seem to be the same, but there's got to be something I'm missing.
In this case, User A has the file checked out
User B can get the latest of this file
User C cannot (even having full admin rights)
Each user is on a different computer, SolidWorks is not open and this is done through Windows Explorer.
Any suggestions.
We did find the cause of the issue. It was due to our systems being imaged with a system image that contained a vault view. Each vault view has a unique ID number, because the system image was copying the same vault view over and over again it meant that users had conflicting vault IDs and this was preventing them from getting the latest version.
The fix is simple, just delete vault view and vault folder and recreate them, a new vault ID will be generated.
That makes sense, as we were imaging our engineering computers.
Your fix worked on the few systems we tested it on.
Thanks for your reply and help!
No problem. That issue caused me a great deal of grief so I remember it well.
Since this issue we have had the system image updated and removed all CAD software, EPDM,
and video card drivers from the image. Things have been much more managable since.
We did find the cause of the issue. It was due to our systems being imaged with a system image that contained a vault view. Each vault view has a unique ID number, because the system image was copying the same vault view over and over again it meant that users had conflicting vault IDs and this was preventing them from getting the latest version.
The fix is simple, just delete vault view and vault folder and recreate them, a new vault ID will be generated.