ugh. Object reference not set to an instance of an object

kmh030 · Post by **kmh030** » Thu Aug 17, 2006 2:30 pm

Help.

We've got 3 respositories, but one of them contains 80% of our source code. Unfortunately I get this error every time I try to connect to it, and consequently I can't check anything in or out. the other 2 repositories are working fine.

I got this error before, and uninstalling/reinstalling the client worked. Not this time. I think I've tried everything and it still doesn't work.

Any help you can give me is much appreciated because I've lost enough hair already I don't need to pull the rest out today =)

Beth · Post by **Beth** » Thu Aug 17, 2006 2:38 pm

Can you tell me what the error is or send me a server log?

kmh030 · Post by **kmh030** » Thu Aug 17, 2006 2:42 pm

"Object reference not set to an instance of an object" is the error...

Beth · Post by **Beth** » Thu Aug 17, 2006 4:05 pm

This was covered off-line.

brentbordelon · Post by **brentbordelon** » Wed Oct 24, 2007 1:42 pm

Beth wrote:This was covered off-line.

Wow, the solution to this really would have helped. You might want to post it?

Beth · Post by **Beth** » Wed Oct 24, 2007 3:51 pm

With this particular error, it's often hard to tell until the logs are examine because it doesn't point to just one thing. I see you started another thread, so I will assist you there.

For others that stumble across this, you may wish to email support at sourcegear.com. You will want to provide a detailed description of what's happening, a zipped up Vault Server Log, and your environment information. An easy way to convey the environment information is to open a Vault client, connect to any repository, and the go to Help - Technical Support and send that information to us.