Status unknown

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
dox

Status unknown

Post by dox » Fri Sep 30, 2005 12:53 am

About a week ago upon logging into my vault account to my dismay all my file status' where listed as "unknown". Strangely I can view differences so the app has obvious access to the local files, but the status remains "unknown". My only choices for being be able to check in my work appears to be either to first overwrite all my local files (defeats the purpose of even having a vault) or create a new folder on vault. Any ideas? Thanks.

Vault Client ver2.0.6(2219)
VB6 Project files

dox

status unknown solution

Post by dox » Fri Sep 30, 2005 1:22 am

It was a missing setting:

Store working folder data inside working folder

fixes this problem

dizn0g
Posts: 1
Joined: Mon Oct 10, 2005 4:39 am

Post by dizn0g » Mon Oct 10, 2005 4:41 am

Does anybody know if this could be affected in this version by using the same login on multiple computers?

If using multiple computers should we setup a different login, even if it is hte same person?

Thanks,
Dox IT Admin

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Mon Oct 10, 2005 7:54 am

Just using multiple computers shouldn't cause this. It depending on how your working directories are set up, how you are retrieving files, and possibly where you state folders are kept.

Unknown files occur when the Vault working directory is set to a directory with preexisting files. If those files have the same name as files in Vault, they are treated as Unknown. Doing a get latest will resolve the unknown file. In Vault 3.x, you can use CRCs to resolve the status of unknown files.

You can also get the Unknown status when cache files have been deleted; and when you do a get to a non-working directory, then make that your working directory, etc.

It's best if a user has a working folder on each machine where they use the Vault client and if all gets are to the working folder, rather than a non-working folder.
If your setup is different, let us know and we may have some suggestions.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply