SourceGearLLC.VaultVsipClient.VsipUtility+AssertionFailedExc

[renatoduran]

Hello guys,

I have a Dot Net project and it was working fine with Vault until today's morning. Suddenly, it started to give the message:

"SourceGearLLC.VaultVsipClient.VsipUtility+AssertionFailedException".

Before that, Vault gave me a message of "Object reference not set to an instance of an object".

I've already tried to exclude my working folder and get the latest version and unbind it from Vault and try to bind it again, with no success.

If I change my working folder to another directory, it works.

Do you know why is it happening? I'm using VS 2005 and Vault version 4.0.3 (15836).

Thanks in advance.

Best regards,
Renato Duran

[Beth]

The error you are seeing doesn't point to one particular thing. I've seen that error with different root causes.

When changing the working folder fixes a problem, it could be because the state file that is directly related to the working folder has some misinformation, or else some other location is also set to the same working folder and that messes with data.

I've seen where a windows update can affect some files. What kind of maintenance does your system go through over the weekend?

[renatoduran]

Helly Beth, thanks for your reply.

In my case, I have only one folder pointing to this working folder I have the problem. You mentioned that the state file could have some misinformation... I didn't understand what exactly it means...

The most important Windows Update I had was last week, on 14th, and it was the Windows Vista Service Pack 2. Do you think this could be the problem's cause? Do I need to verify something else?

Thanks a lot!

Best regards,
Renato Duran

[Beth]

You don't really need to know anything about the state file. It's just something that manages the working folder.

Where did you switch the working folder at? What exact steps did you take?

With updates, I've just sometimes seen updates sometimes get in the way. Usually, a reinstall of the software fixes whatever connection it lost to the resource it needed. I don't have anything consistent that says any particular update always causes a particular problem. It's fairly random.

[Beth]

In addition, I think you will get much better results if you upgrade your clients and server to Vault 4.1.4. That would be a free upgrade from Vault 4.0.3 and would get you all the fixes for the Vault 4.x.