Unable to Access Repository

[pug]

Hi I am having trouble accessing one of our repositories. I can access others, but this one is giving the "Object not set to an instance of an Object" message. I have tried clearing my client cache which didn't work. The strange thing is, one of my colleagues can access the repository if he signs on to my client on my machine....Any ideas gratefully accepted on this one.

Meant to say it is version 4.1.1

Update: Have been looking at logs and some of my colleagues activities are generating errors along the following lines:

System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK__#release__A10A8E2267DE6983'. Cannot insert duplicate key in object 'dbo.#releaselistitems'.

Not sure if this is relevant...

Thanks

[lbauer]

It still sounds like a cache issue.

I don't know how you reset the cache, but let's try this:

I'd suggest renaming the Vault_1 file and allow a new to be created. This folder is in

%USERPROFILE%\Local Settings\Application Data\SourceGear\Vault_1\Client\{repository-guid}\{vaultuser}\

On Vista/Win7 that path is:
%USERPROFILE%\\AppData\Local\Sourcegear\Vault_1\Client\{repository-guid}\{vaultuser}\

So the steps would be:

Close any open clients, Vault Client, Visual Studio, etc.
Rename Vault_1.
Restart IIS, which restarts the Vault Server
Then open your client and re-connect.
You'll need to reset working directories.

Let me know if this does not resolve the problem.

[pug]

Hi thanks for the quick response. What will happen to working directories if I reopen my Visual Studio project? I also am unable to bind to any source provider in Visual Studio, does that change anything?

[pug]

Hi renaming vault_1 worked. After a bit of messing with Visual studio it's more or less back where it was. Thanks for you help. Am I safe to delete the vault_1 folder and it's contents?

[lbauer]

Glad that worked for you. Yes, you can delete the old Vault_1 folder, now that you have the new cache reestablished.