Problem with Vault 4.0.2 Checkout

msauper · Post by **msauper** » Mon Aug 06, 2007 10:23 am

We upgraded from 3.5 to 4.0.2 and all users are working fine except one.

This person gets a "null object exception" each time they check out a file. The file is marked as checked-out in vault. However, the file is still read-only on disk. Check-in also get a "null object exception".

[EDIT] We did try uninstalling/reinstalling the client to no avail.

Any suggestions?

Best regards,

Metro.

ian_sg · Post by **ian_sg** » Mon Aug 06, 2007 10:33 am

Metro,

Can you have this user turn on logging for the Visual Studio 2005 client, and send me a log that shows this error? You can post it here or email it to me: ian at sourcegear dot com.

Thanks.

msauper · Post by **msauper** » Mon Aug 06, 2007 2:00 pm

Ian,

After reviewing the debug log, I was able to identify that Vault was having a problem updating the Pending file.

I renamed CacheMember_ChangeSetItems to CacheMember_ChangeSetItems.OLD and the client was then able to check-out and check-in without an error.

Is this an acceptable solution? Did I loose anything from the CacheMember_ChangeSetItems file that I renamed?

Best regards,

Metro.

ian_sg · Post by **ian_sg** » Mon Aug 06, 2007 2:07 pm

What would have (potentially) been lost here is any pending changes that don't correspond to a file's contents changing. If you had any pending moves, renames, deletes, branches, shares, etc. they will no longer appear in your pending changeset, and you'll have to re-pend them.