Check-in: Object reference not set to an instance object

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

Moderator: SourceGear

Post Reply
VVerma
Posts: 4
Joined: Thu Mar 13, 2008 2:27 am

Check-in: Object reference not set to an instance object

Post by VVerma » Thu Mar 13, 2008 2:44 am

Hi,

We are encountering an issue while checking-in any code file on Vault.

The error states: "Object reference not set to an instance object"

Request you to kindly provide us the solution to rectify the same.

Thanks,
Vijay

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Thu Mar 13, 2008 9:19 am

Which version of Vault are you using?

Are you checking in using the Vault client, the Vault command line, or Visual Studio? If you are using Visual Studio, which version?

VVerma
Posts: 4
Joined: Thu Mar 13, 2008 2:27 am

Post by VVerma » Thu Mar 13, 2008 9:46 pm

I am using Vault Version 4.0.5 and Visual Studio .Net 2005

I am checking-in the code thru VS .NET and Vault too.

Please help!

Vijay

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Fri Mar 14, 2008 10:22 am

You shouldn't be bouncing between Vault and VS for check ins. Do you get the error when using Vault for the check in or when using VS?

The problem with using both for the same functions is that almost always, people end up with the working folder in Vault set differently than the working folder in Visual Studio. When using IDE integration, Visual Studio has to run the show, especially with anything that involves setting the working folder.

If you ever can't check in through VS, then rather than switching over to Vault, why it won't check in in VS should be looked at and fixed. Usually, it's a binding issue that can be resolved in just a minute or two.

Is the file you can't check in, checked out through Visual Studio? Can you check it in through Visual Studio?

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Fri Mar 14, 2008 2:37 pm

Also, you can try clearing your Client Side Cache. You will want to keep the cachemember_workingfolderassignments, and afterwards perform a Get with the option "Do Not Overwrite/Merge Later

VVerma
Posts: 4
Joined: Thu Mar 13, 2008 2:27 am

version.xml

Post by VVerma » Mon Mar 17, 2008 1:00 am

An error occurred when trying to connect vault client giving error " retrieve version.xml file from the SourceGear website

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Thu Mar 20, 2008 5:44 pm

That function is only for displaying what version we have most recently posted on our website. It's not needed for source control. You can turn this off in the GUI Client under Tools->Options->General->Check for latest Vault version at startup.

Was everything else fine?

Post Reply