MSI failed on isntall error 2709
Hello folks,
I was wondering if anyone has encountered error 2709 when trying to install one of their msi packages on the same or different machine and if so what can I look at to resolve the issue. I looked through the msi error codes on the appdeploy website but didn't find too much info about it.
I'm using vs 1.2 on a virtual, Windows 7 64-bit machine.
Thanks for your time
I was wondering if anyone has encountered error 2709 when trying to install one of their msi packages on the same or different machine and if so what can I look at to resolve the issue. I looked through the msi error codes on the appdeploy website but didn't find too much info about it.
I'm using vs 1.2 on a virtual, Windows 7 64-bit machine.
Thanks for your time
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
didn't find too much info about itReally?!?
That seems pretty straightforward to me! You clearly don't validate your MSIs and, if you use an authoring tool, you probably ignore the warnings provided. For example, Wise Package Studio will show the offending row in red. That row will be in the Registry of File table, I expect.
Posted by:
Hirsch18
13 years ago
Take it easy bud, this was my first time attempt at creating an msi so when I saw the error It wasn't 100% clear what the issue was. I guess I should have asked what "The specified Component name ('[2]') not found in Component table" meant.
Posted by:
Nicole
13 years ago
It means, that something belongs to the component ('[2]') (could be a file, or a reg-key,...), but this component does not exist.
Let the file (or whatever) be a part of another component, if possible, or create a new component.
Let the file (or whatever) be a part of another component, if possible, or create a new component.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.