2.0.6 client Check-In does nothing for setup & msi files

[luther_miller]

We created a "Release" folder under a VS.NET solution in Vault and checked in the Setup.exe, Setup.ini, and the MSI files into Vault. Later, we checked them out and did a new release build. After the build, in the Vault client the status became "Unknown" for each of the three files.
WHen we selected the three files and tried to check them in, the cursor blinked for a split second but nothing at all hapoened. There were no messages at all and we could go back to doing other things in Vault immediately. The developer experiencing this was on 2.0.3 and we upgraded to 2.0.6 and that did not make a difference. We can delete the files and re-add them, but does not appear that we can check them out, rebuild them, and check them in. We also tried deleting the whole Release folder from Vault and re-adding it and that also did not make a difference.

Any idea what is going on here and how we can fix it?

[dan]

The problem is the Unknown file status. See http://support.sourcegear.com/viewtopic.php?t=162 and http://support.sourcegear.com/viewtopic.php?t=131 for explanations of Unknown files. Somehow the baseline file got removed, or a new working folder was set where the file already existed (without having done a Get from Vault on the file)

Vault 3. 0 automatically resolves Unknown files, but in 2.0, you'll need to do a Get Latest to clear it out.