Login problem after upgrade from 3.1.8 to 4.0.4

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
jmlange
Posts: 32
Joined: Tue Jul 13, 2004 8:56 am

Login problem after upgrade from 3.1.8 to 4.0.4

Post by jmlange » Mon Oct 08, 2007 8:15 am

One of our Vault users is having a login problem now that we have upgraded to version 4.0.4 of Vault. He has installed the 4.0.4 client. When he tries to log in, he gets an error dialog telling him that a certain file already exists.

He's then not allowed to do anything and it won’t let him connect or see any of the folders.

I've had him turn on client logging and I have a VaultGUIClient.txt file if that would be helpful.

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

Post by Beth » Mon Oct 08, 2007 9:26 am

It could be that there is some kind of invalid operation pended in the Client Side Cache. Have your user go into his cache, located in %USERPROFILE%\Local Settings\Application Data\SourceGear\Vault_1\Client\{repository-guid}\{vaultuser}\, and remove the CacheMember_KnownChanges. Then have the user restart his Vault client and try again.

jmlange
Posts: 32
Joined: Tue Jul 13, 2004 8:56 am

Post by jmlange » Tue Oct 09, 2007 8:51 am

Even after deleting that file, and others in that cache folder, I still have one user getting the error. Would it be safe to just clear the cache? Any other suggestions?

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

Post by Beth » Tue Oct 09, 2007 9:57 am

You can clear the entire cache including the _sgvault folder, but I would recommend keeping CacheMember_WorkingFolderAssignments, otherwise the user may have to reset all their working folders.

Can you post a screenshot of the error?

jmlange
Posts: 32
Joined: Tue Jul 13, 2004 8:56 am

Post by jmlange » Tue Oct 09, 2007 10:18 am

I'm attaching a screen image of that error.
Attachments
Vault error.doc
(362.5 KiB) Downloaded 414 times

jmlange
Posts: 32
Joined: Tue Jul 13, 2004 8:56 am

Post by jmlange » Tue Oct 09, 2007 10:42 am

Clearing the cache, with the exception of CacheMember_WorkingFolderAssignments, did the trick. That user is able to log in successfully now.

Thank you!

Locked