If you are having a problem using Vault, post a message here.
Moderator: SourceGear
-
ww
- Posts: 33
- Joined: Tue Aug 16, 2005 7:33 am
Post
by ww » Thu Oct 18, 2012 8:59 am
I'm trying to upgrade from 5.0.2.18753 to the current version. The installer prompted me for the MSI file for the old version, which I gave it. Setup then failed with error "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753."
I reran setup with MSI logging turned on and got the same failure. The log shows this:
MSI (s) (C4:CC) [10:52:35:892]: Doing action: CustomActionExe.exe_1
Action 10:52:35: CustomActionExe.exe_1.
Action start 10:52:35: CustomActionExe.exe_1.
MSI (s) (C4:CC) [10:52:35:892]: Note: 1: 2753 2: CustomActionExe.exe
DEBUG: Error 2753: The File 'CustomActionExe.exe' is not marked for installation.
Should I remove the old version and retry the installation?
-
Beth
- Posts: 8550
- Joined: Wed Jun 21, 2006 8:24 pm
- Location: SourceGear
-
Contact:
Post
by Beth » Thu Oct 18, 2012 9:30 am
Go to your Control Panel and see if you can perform an uninstall first or see if it's even listed there.
Then find your command-prompt icon, right-click it and select Run As Administrator. Then use that to run the installer. Often just running the installer as-is doesn't allow you to have enough privileges, even when you are an administrator.
Beth Kieler
SourceGear Technical Support
-
ww
- Posts: 33
- Joined: Tue Aug 16, 2005 7:33 am
Post
by ww » Thu Oct 18, 2012 9:40 am
This is on Windows Server 2003, so there is no Run as Administrator.
The old version is still listed in Add/Remove programs. I got the same 2753 error when I tried to do the uninstall from there.
-
Beth
- Posts: 8550
- Joined: Wed Jun 21, 2006 8:24 pm
- Location: SourceGear
-
Contact:
Post
by Beth » Thu Oct 18, 2012 2:39 pm
Do you have a client on this machine as well? If so, let's uninstall the client.
Then I'm going to have you perform a manual uninstall of the server.
- 1) Backup your sgvault and sgmaster databases if you haven't already.
2) Perform a registry backup.
3) If you have shadow folders, make a backup of the web.config under vaultservice/vaultshadowfolder.
4) Open your IIS Manager and delete the vaultservice, vaultshadowfolder, and sgdav folders.
5) Delete the vaultapppool from your Application Pools.
6) Check the location on disk that you installed Vault to. The default is C:\inetpub\wwwroot. Make sure there isn't still a vaultservice folder present.
7) Open your registry and search for the word SourceGear. Specifically you are interested in finding folders called SourceGear and anything under Windows\currentversion\install or Windows\currentversion\uninstall. Carefully remove component entries for SourceGear Vault. You will find some where SourceGear shows up as an entry under a folder that is a GUID. In some cases the entire GUID is related to only SourceGear and you can remove the GUID. If you would like assistance with this section, just contact me in support.
Then try your install again.
Beth Kieler
SourceGear Technical Support
-
ww
- Posts: 33
- Joined: Tue Aug 16, 2005 7:33 am
Post
by ww » Sun Nov 18, 2012 7:51 pm
I finally had time to get back to this, and following these steps worked.
-
Beth
- Posts: 8550
- Joined: Wed Jun 21, 2006 8:24 pm
- Location: SourceGear
-
Contact:
Post
by Beth » Mon Nov 19, 2012 9:27 am
Thank you for the update. I'm happy to hear you're working.
Beth Kieler
SourceGear Technical Support