Apparently hung install, Vault Client 3.1.6
Moderator: SourceGear
Apparently hung install, Vault Client 3.1.6
Installing Vault Client 3.1.6 onto XPSP2.
The dialog says 0 seconds left, but the button says Cancel still.
I see no indication that it is alive -- it may be dead/hung -- I'm not sure how long to give it before giving up on it...
The dialog says 0 seconds left, but the button says Cancel still.
I see no indication that it is alive -- it may be dead/hung -- I'm not sure how long to give it before giving up on it...
Tried cancel, now it's apparently worse
I pushed Cancel, chose Exit Install, and it still appears to be hung as before, but now the Cancel button is dead.
Gets worse and worse...
Cannot logoff, cannot shut down, cannot reboot.
Vault installation appears to have completely hung the machine.
Hard reboot is apparently the only answer, and hope Vault didn't corrupt the Windows Installer database.
Vault installation appears to have completely hung the machine.
Hard reboot is apparently the only answer, and hope Vault didn't corrupt the Windows Installer database.
("You must select a topic to reply to" bug is still present in forums)
I tried to uninstall that Vault 3.1.6, and the uninstall hung, and I hit cancel, and that hung. I had to use the cold off button.
Now Vault 3.1.6 is not listed in the Add/Remove, but the files are still present on the hard drive.
What should I do next? (Should I try to reinstall it, in order to try to re-uninstall it?)
I tried to uninstall that Vault 3.1.6, and the uninstall hung, and I hit cancel, and that hung. I had to use the cold off button.
Now Vault 3.1.6 is not listed in the Add/Remove, but the files are still present on the hard drive.
What should I do next? (Should I try to reinstall it, in order to try to re-uninstall it?)
Both XPSP2 and 2003SP1 lacking Add/Remove entries for Vault
(You must select a topic to reply to)
The machine where the uninstall hung, and now SourceGear Vault is missing from Add/Remove, is Windows XPSP2.
I see another machine (2003SP1) which has SourceGear Vault 3.1.7 installed, and which also lacks an entry in Add/Remove.
The machine where the uninstall hung, and now SourceGear Vault is missing from Add/Remove, is Windows XPSP2.
I see another machine (2003SP1) which has SourceGear Vault 3.1.7 installed, and which also lacks an entry in Add/Remove.
You could attempt a reinstall and uninstall -- might be safer than editing the registry, etc.
You must be logged in before you can post. Hitting "reply" and then logging in causes the message you are seeing. We can debate whether this is a bug or not, but since we didn't create the forum software, it's just the way it works.
("You must select a topic to reply to" bug is still present in forums)
You must be logged in before you can post. Hitting "reply" and then logging in causes the message you are seeing. We can debate whether this is a bug or not, but since we didn't create the forum software, it's just the way it works.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
> We can debate whether this is a bug or not
I wasn't trying to debate it at all -- actually, it never occurred to me that some might find it desirable to deliberately send users to an error page. I had merely assumed without thinking about it, that it was a mistake, and that you had meant to send the user to the page to post the response (after the user hit Post, I mean), and that someone screwed up somewhere in the code, and (I had kind of idly guessed) use an uninitalized variable somewhere, thus causing the error. So I had no idea that bug might be considered a feature.
I wasn't trying to debate it at all -- actually, it never occurred to me that some might find it desirable to deliberately send users to an error page. I had merely assumed without thinking about it, that it was a mistake, and that you had meant to send the user to the page to post the response (after the user hit Post, I mean), and that someone screwed up somewhere in the code, and (I had kind of idly guessed) use an uninitalized variable somewhere, thus causing the error. So I had no idea that bug might be considered a feature.
By the way, is this common for SourceGear Vault to not have a working uninstall? (Now that I see it on two different computers, with different operating systems, I wonder if it is a trend.)
What I was really hoping, was a response saying that it was a bug in 3.1.6, and that it has been fixed, and that the workaround is -- <some link to a series of steps...>
What I was really hoping, was a response saying that it was a bug in 3.1.6, and that it has been fixed, and that the workaround is -- <some link to a series of steps...>
Error 1705 ?
> You could attempt a reinstall and uninstall...
I tried a reinstall -- I got
Error 1705: A previous installation for this product is in progress. You must undo the changes made by that installation to continue? Do you want to undo those changes?
Yes/No
?
I tried a reinstall -- I got
Error 1705: A previous installation for this product is in progress. You must undo the changes made by that installation to continue? Do you want to undo those changes?
Yes/No
?