Bug #12318
Error 2869 on installing (Win7 x64)
| Status: | New | Start: | 2010-07-25 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | % Done: | 0% |
||
| Category: | Installation | |||
| Target version: | - | |||
| Votes: | 3 |
Description
(Different error code to #11780)
I've removed the product code (BAF18434-6E45-4911-99C6-BD2EC65443F4) from the MSI database and I still get error 2869 when installing the new version.
Please could you make a 7zipped version for people to more simply work around this issue?
History
Updated by Yoma about 1 month ago
- Category set to Installation
- Assigned to set to Yoma
For now:
Download the Windows Installer Cleanup tool
http://support.microsoft.com/kb/290301
And use it to remove the previous installation.
Then try installing the latest version of addonsync.
The MSI installation must have somehow gotten corrupted.
BTW that tool is handy for all sorts of similar msi issues!
I'll look into providing a separate file later, however it creates a bit more room for error as well.
Updated by zx64 about 1 month ago
"This article previously contained a link to the Windows Installer Cleanup utility (MSICUU2.exe). If you were directed to this article to solve a problem installing a product other than Microsoft Office, please contact your software manufacturer for installation support on the product."
I used msizap (finding that was a chore in of itself) to remove the product code from the MSI database.
I still have the problem.
Updated by Yoma about 1 month ago
Hmm using msizap manually might have created a bigger problem then there was... The installer cleanup thing that was on that article kind used msizap to completely remove the msi, but it uses specific parameters...
Do you have any idea how you actually got into this situation? Did you alter files in the program's installation folder?
May i presume you do run the installer as admin?
I know the msi's are a bitch, but i'm too lazy to create an other installation method and the msi's created by VS2005 are known to have some trouble on some systems.
I'll look at creating a 7z file.
Besides all this, this "project" has taken up a lot more time then i expected. I'm considering investing my time in other, more useful stuff. Especially as BIS is working on a sync of their own and the whole project will probably soon be redundant.
Using 7z files will have issues of it's own.
Updated by Yoma about 1 month ago
Btw: this error does not allways occur (works perfectly fine on my win7 x64)
Just out of curiosity:
Did you install the tool in a custom folder ?
(not in Program Files (x86)\YomaTools\Addon Sync 2009 )
Updated by CameronMcDonald about 1 month ago
I've had this problem for ages, and it occurs whether installing in the default folder or not. :)
Would like to see it sorted, please.
Updated by CameronMcDonald about 1 month ago
Stopgap solution for those having trouble.
Open cmd dialog:
msiexec /a pathtotheinstaller.msi
Works fine. :)
Updated by Yoma about 1 month ago
- File msicuu2.exe added
This microsoft tool should do the trick better...
Just install it, fire it up, remove AddonSync2009 through it, reboot (normally not needed), and reinstall the tool.