MIS has just been "migrating" everone from a user on 1 domain to a user on a new domain.
As part of this process the profile of the old user is copied to the new user.
Once this happens it seems the Vault client doesn't work from the new user.
Reinstalling the Vault client has worked for some people, but not for others.
What I see either when attempting to install/reinstall the vault client OR to uninstall the client, is a message which I think is requesting the path to the msi file for the Vault client currently installed.
I'm posting this because we now have 1 user who can't get a Vault client installed. Somehow cancelling through the many requests for the (old?) msi during an attempted install of the 3.1.9 client (which did report it succeeded at the end, although it wasn't) and the uninstall of the various Sourcegear Vault clients found in Add/Remove Programs (also cancelling requests for the msi) has totally messed something up.
We also tried logging back in as the old user and uninstalling and reinstalling Vault (which worked), and then uninstalled it from that user (which succeeded) before trying to reinstall the Vault client again on the new user (which once again failed).
I can't say exactly what version of the client people had installed on their machine prior to the migration (our server is 3.1.6, and I had recommended that everyone upgrade to that client version, but I know not everyone did).
I'm at a loss as to how to get the Vault client to work on this person's new user account on their computer.
Mike
Vault Client Install Fails
Moderator: SourceGear
Vault Client Install Fails
- Attachments
-
- Vault client install error dialog
- VaultInstallError.JPG (44.38 KiB) Viewed 2081 times
Mike:
We've seen this before when someone did not have all of the environment variables configured correctly. The Domain switch may have caused some of the Required Windows Environment Variables to not exist or exist in a folder where permissions do not allow access.
Can you have the user check out this problem - See You receive an "Error 1606" error message when you try to install or remove a Microsoft program - http://support.microsoft.com/?kbid=886549 for more information.
We've seen this before when someone did not have all of the environment variables configured correctly. The Domain switch may have caused some of the Required Windows Environment Variables to not exist or exist in a folder where permissions do not allow access.
Can you have the user check out this problem - See You receive an "Error 1606" error message when you try to install or remove a Microsoft program - http://support.microsoft.com/?kbid=886549 for more information.
Jeff Clausius
SourceGear
SourceGear
Jeff,
I got the Vault Client installed and working on my user's new account on his machine.
The suggestion above wasn't the problem, but it got me looking through the registry for entries that still referred to his old user's files, and I found the key [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\CFAE0BA6442A65B48914BEC199FC51EA] with entries that referred to the Vault client AND happened to look like the GUID that was showing up in the error dialog we were seeing.
I deleted that key and the Vault Client installed w/o any more problems. (Although I also had to edit the Vault HKCU CacheLocation to point to his new user's local settings directory).
Mike
I got the Vault Client installed and working on my user's new account on his machine.
The suggestion above wasn't the problem, but it got me looking through the registry for entries that still referred to his old user's files, and I found the key [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\CFAE0BA6442A65B48914BEC199FC51EA] with entries that referred to the Vault client AND happened to look like the GUID that was showing up in the error dialog we were seeing.
I deleted that key and the Vault Client installed w/o any more problems. (Although I also had to edit the Vault HKCU CacheLocation to point to his new user's local settings directory).
Mike