SourceGear Support

mlippert wrote:Thanks for your help figuring this out Beth, and Jeff...

Yes, thanks.

And sorry for sounding frustrated. But as you can imagine, this has been festering for a while and was driving me nuts.

I appreciate your working through it.

The virus scan is a good idea, when the new user was created and the old profile mapped over, MIS also changed the virus software that we run from Norton to McAfee. They might have it set so that it is scanning those files. I hadn't heard back on the virus scanning part or else I missed it. Could y...

The virus scan is a good idea, when the new user was created and the old profile mapped over, MIS also changed the virus software that we run from Norton to McAfee. They might have it set so that it is scanning those files. I hadn't heard back on the virus scanning part or else I missed it. Could y...

Details on client-side logging can be found here: http://support.sourcegear.com/viewtopic.php?p=5375 Oh, and the unbinding from VS would only be happening on the one client machine, not with anyone else. VS and Vault can sometimes be looking in different places for their information, which is why I...

mlippert wrote:We do have Gold Support, Kent just didn't have the #'s to enable his user for it.

Ah. Yeah, I didn't realize that was an issue. I've associated my user id with our Gold Support number now, in case that matters. Beth, please let me know if I need to re-post this on the other forum.

You can send the log either using the private function here or to me directly at beth at sourcegear.com and just reference this post. Ok. I'll send it momentarily. Can you tell me what version your Vault Server is? 3.1.6.3658, same as my client. I'm told we're going to a newer version (not sure whi...

The file it is referencing in the error you sent me looks to be in the client side cache, which is why I said what I did. Yes, renaming it should have forced it to make a new one unless something else unexplained happened. Right. With the re-install did you check your registry to make sure that the...

The file it is referencing in the error you sent me looks to be in the client side cache, which is why I said what I did. Yes, renaming it should have forced it to make a new one unless something else unexplained happened. Ok. With the re-install did you check your registry to make sure that there ...

The first thing I'd probably try is closing vault, clearing your Client Side Cache , then restart Vault and try to set your working folder again. Thanks for the suggestion, Beth, but isn't this something I've already tried? That is, didn't I effectively clear it when I said I renamed C:\Documents a...

Doing "Set Working Folder" recursively (by clicking the "force all subfolders" checkbox) on a tree I have set many times now says: The process cannot access the file "C:\Documents and Settings\kpitman.PTCNET\Local Settings\Application Data\SourceGear\Vault_1\Client\C532E938-...