Object reference not set to an instance of an object.

[Kenneth E.]

Hi there,

I've just started to use vault on a .net solution. However, I have some strange problems with it. The error message with the null reference is comming when I'm trying to check in my changes. No matter which file I try, it fails. At the same time I'm locked out of the repository when using the vault client - I am simply told that I don't have rights anymore (I'm using the free single user setup, with one admin). I tried to use the HTTP Admin client to add rights manually on folder levels etc., but the only way to fix the problem was to remove the repository and create it again.
After fixing it the first time with a fresh repositiry, I thought everything was good, but now I'm facing the problem again - and I have worked less than 2 hours on the project.

What I do know is that I have renamed, deleted and moved a lot of the files, and this may be more than vault was able to handle in one transaction. However, it scares me that I have no way to get the repository back - the only option is to remove it, which sort of defeats the idea of using a source versioning tool. Maybe a security check/reset mecanism or similar function would be good to have in the http admin.

[jeremy_sg]

This is very odd, and there is definitely an easy workaround, but before you fix the problem, could you turn on Vault client logging and reproduce the problem? We need that to be able to fix the cause of the problem.

Once you've reproduced the problem in a log file and sent that log file to us, delete your client cache files to cause the client to refresh its cache.

[Kenneth E.]

Thanks for your very quick response. I'll make sure to log the problem next time with the Vault client (if I can reproduce it).

Also great to know that it is possible to fix it just by deleting the cache.

Thanks again!