Renamed Repository still shows old name in Client Tool
Moderator: SourceGear
Renamed Repository still shows old name in Client Tool
Hi,
After renaming a repository, the old name still shows in the Caption of the Vault client? Is there something else that I need to change?
Thanks.
After renaming a repository, the old name still shows in the Caption of the Vault client? Is there something else that I need to change?
Thanks.
I also have a problem when I delete a folder and obliterate it.
Then thru Visual Studio 2005 I try to add it to the vault, I can't because the old folder still shows grayed out? How can this be if it was permantely destroyed?
If I try to add it to vault , I get this error :
Project node count mismatch
I am using the 4.02 install.
Then thru Visual Studio 2005 I try to add it to the vault, I can't because the old folder still shows grayed out? How can this be if it was permantely destroyed?
If I try to add it to vault , I get this error :
Project node count mismatch
I am using the 4.02 install.
We're investigating the repository rename, but the report that concerns me is the Project node count mismatch. Those issues should all be resolved by now, but something seems to be busted for you. Can you turn on Vault client logging and post the exception from the log file? That would help us track this down. It would also be helpful to know if you have any odd project types that Vault may not be handling well.
I've reproduced the repository rename problem. You can get the client to correct itself by deleting the CacheMember_Repository client cache file.
Hi Jeremy.jeremy_sg wrote:I've reproduced the repository rename problem. You can get the client to correct itself by deleting the CacheMember_Repository client cache file.
The same thing about the Window Caption is happening to me. I have deleted CacheMember_Repository alone, with CacheMember_LastStructureGetTime and even the whole folder, and nothing made it work. Would you have any idea where the wrong caption is coming from?
Thanks in advance.
I'm not sure. You could try doing an iisreset on the server to force it to reload the name of the repository (you'll probably need to delete the repository cache file again as well).
Another thing to watch out for is that you're deleting the correct repository cache file, as it's often hard to tell which is which among the GUIDs in the cache folder.
Another thing to watch out for is that you're deleting the correct repository cache file, as it's often hard to tell which is which among the GUIDs in the cache folder.
Thank you guys for the prompt answers.
A reset did it... should have thought of that.
And about the GUIDs, yes, it is difficult to tell which one to delete from, but I had a look at the contents of the CacheMember_Repository and saw the repository name right in the beginning of it. That directed me to the right one.
Once again, thanks a lot.
A reset did it... should have thought of that.
And about the GUIDs, yes, it is difficult to tell which one to delete from, but I had a look at the contents of the CacheMember_Repository and saw the repository name right in the beginning of it. That directed me to the right one.
Once again, thanks a lot.