Status Unknown

[dsalter]

I have a rather interesting issue that I think is the result of me working off of 2 different workstations at 2 different locations.

I have a need to work between locations. At my primary location (LOC A), I have a desktop PC. My secondary location (LOC B) has a laptop that I can use to travel elsewhere. Last week, at LOC B, I worked in SSIS 2008 and Vault 5.1.1. I had items checked out to a shared network location (S: drive).

Late last week, the laptop died. I managed to shelve all my changes just in case such an unfortunate incident occurred.

Today, I am at LOC A on my desktop. I go into the Vault client and see that all of my checked out items are "unknown". I checked to ensure my local working copy is the network S: location.

When I go into SSIS 2008 and open the solution from Vault, all items show as renegade, but hovering over them tells me I have them checked out. I have attached a screen shot.

I think the problem is this........ The laptop from LOC B stored vault settings locally, in the local user profile area. Now that the laptop is gone, that location is also gone. The other part of the problem is I believe each site had its own profile setting for my network logon. LOC B initially could not "talk" to the vault server at LOC A, so ports needed to be opened for the communication. Perhaps this issue could have been solved had I used the settings in Vault to have my vault settings stored on a network location accessible by both LOC A and B.

Currently, I am in a situation where I am considering undoing all my check outs, checking back out and unshelving my changes. I want to make mention of the above and see if you think the issue is as I think it is. Or, perhaps there is a setting in the Vault client for those of us working between various locations, but needing to open and work on the same project.

Thanks,
Don

-------

Further to:

I just checked the properties of one of the files I have checked out in Vault Client and the machine name is different than the machine name of my desktop. This is again likely because my laptop logs on at LOC B and desktop at LOC A. Could this difference in machine name be causing my problem. Vault recognizes the files are checked out by ME, but at the same time, only shows them as renegade to me. When I get latest, they show checked out to me, but not with a red check mark, but a little man (who is also me!). They are mine, but not mine on my desktop at LOC A.

Another screen shot is attached on this.

[lbauer]

The Vault client stores information about the folder tree, checkouts, pending change set, working folders,etc. in the client-side cache. Also, when you do a Get, the Vault client stores baselines of the files and compares files in the working folder to this baseline to determine the file status in the working folder.

These cache files are generally stored in the user's Local Settings directory, and are unique per client machine. The problem comes when you use the same working folder for more than one machine.

For example, if the Vault client on Machine A checks out a file and modifies it, the status is Edited. However the Vault client on Machine B, using the same working folder, sees the file as Renegade ( modified but not checked out), since the file was not checked out from Machine B.

"Unknown" status files happen when the client detects files in the working folder with the same name as those in the repository folder, but it has no baselines for it. This can happen when the working folder changes to a folder with pre-exisitng files, or if the baselines are deleted.

If you are going to work on different machines using the same network working folder, one thing to try is to store the baselines in the working folder itself, so both clients will have access to the same baselines.

This setting is in the Vault client under Tools -> Options -> Local Files -> Cache Location -> Store Working Folder State/Baseline Files.

After you set this, do a Get Latest to re-create the baselines. Be sure to back up any modified files first.