Trying to figure out what "Unknown Status" means in the staus column. Looked in the help and that didnt explain much. Its pretty simple to fix this (either refresh from Inventor>Vault browser or "Get" from Vault).
I just dont understand how it get this way or the hidden implications of correcting it either way.
Thanks,
Kirk
It typically means that an iteration/edit/save of the file has been happened without it being checked out. There's a load of ways it can happen, sometimes avoidable but often not.
One example is the Inventor IPJ file, if you clear the read only flag on the IPJ and make a change, you'll get the unknown status flag against it. If you move files around in the workspace, rename them etc that can cause it. Inventor can also cause it by editing files that aren't checked out <- that's the most frustrating and disruptive occurence of this.
But either way, it usually means that the version of the file in the workspace has been altered without a checkout.
It also could mean that Vault is unable to verify the checksum of the file. If you know you have not modified the file you can just do a Get to get the latest version.
Kirk,
This would have nothing to do with the other user checking out and modifying a file. Did you perform a update of Vault recently?
How clean is your workspace? Is it possible for you to check in all files you have checked out, delete all local files and get all the latest ones from Vault again?
There was change made recently to help with the "edited out of turn" issue.
Durring donwloads we now store more infomraiton is some hidden files within the workspace.
The "unknown" status can happen for a couple reasons.
1. Vault can not read the file correctly for some reason
2. The local data (hidden by default) is not present. This can happen a couple ways.
3. The file on disk is historical data and coresponding version is Vault has been purged.
Hope this helps
There is some backup logic to get the status in the event of a missing v file.
But you are rolling the dice, there are many scenerios where you will get an unknown status if you delete the v files.
I dont recommend it.
I only deleted the local _v files as a test.... just to see if I could make the Unknown Status icon appear in the vault browser. After I deleted them, the icon did not appear in the browser.
On a different workstation, here is what I see in the Vault browser. I have the _V folder open and the file selected in the foreground. A few things I would like to note. 1. there is only one version of the file in vault. 2. This was checked in by EWest and this is EWests workstation we are looking at. 3. The _v is in the folder. 4. The Hidden files/folders were hidden on this system, I had to make them visible.
We have not copied any of the _v files to this folder.
The checksum should not change when moving a file from one location to the next.
But I suppose it is possible depending on how you moved them. A checksum change typically only occurs is the file itself has changed.
However, we also use other information that could be changed on a move like this. For example the create date of a file. We use the create date of the file to help identify the version. When moving files through HTTP, FTP, or if moving from an NTFS disk to a non-NTFS disk then the create date will be changed. When we download from Vault (via HTTP) we reset the create date to the correct value. If the create date of the file has been changed, then you may get an unknown status.
Also, in the workspace we place hidden files into hidden folders. Depending on your copying process those files might have been left behind. If those files are not present when they should be then Vault also can not identify the version correctly.
We typically recommend the people not manually move the workspace. The most reliable way is to check-in the data and re-download from Vault on the new machine.
