By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,795 Members | 1,761 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,795 IT Pros & Developers. It's quick & easy.

Running Setup project causes error code 2709

P: n/a
Hello,

I've created a setup project and when I run the .msi I get the following
message.

"The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2709."

What causes this error message?

Regards
Simon Jefferies
Tools Programmer, Headfirst Productions
mailto:si****@headfirst.co.uk
www.headfirst.co.uk www.callofcthulhu.com
-
Nov 20 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Hi Simon,

Thanks for posting. According to the Windows Installer Platform SDK
document, 2709 means the following:

The specified Component name ('[2]') not found in Component table.

There seems to be some problem with the MSI package. Do we have the problem
if we rebuild it?

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Nov 20 '05 #2

P: n/a
Thanks for your reply,

The problem still occurs when I rebuild it.

Simon Jefferies
Tools Programmer, Headfirst Productions
mailto:si****@headfirst.co.uk
-

"Felix Wang" <v-*****@online.microsoft.com> wrote in message
news:ME****************@cpmsftngxa10.phx.gbl...
Hi Simon,

Thanks for posting. According to the Windows Installer Platform SDK
document, 2709 means the following:

The specified Component name ('[2]') not found in Component table.

There seems to be some problem with the MSI package. Do we have the
problem
if we rebuild it?

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Nov 20 '05 #3

P: n/a
Hi Simon,

Are you using some third party merge modules in the setup project?

In addition, if we create a new setup project, do we have the same problem?
We may need to use some Windows Installer Platform SDK tool to further
track the issue:

HOWTO: Use the Orca Database Editor to Edit Windows Installer Files
http://support.microsoft.com/?id=255905

We can use Orca to perfom an consistence check of the MSI generated.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Nov 20 '05 #4

P: n/a
Hello,

There are no third party merge modules in the setup project.

I have created another setup project and it appears to be working, something
to do with this project in particular causing the problem?

I've actually tried ORCA with it to validate the msi it generated and I
didn't see anything relating to this item.

Would it be helpful to attach the msi? or is there something else I can try?

--
Regards
Simon Jefferies
Tools Programmer, Headfirst Productions
mailto:si****@headfirst.co.uk
www.headfirst.co.uk www.callofcthulhu.com
-
"Felix Wang" <v-*****@online.microsoft.com> wrote in message
news:dM**************@cpmsftngxa10.phx.gbl...
Hi Simon,

Are you using some third party merge modules in the setup project?

In addition, if we create a new setup project, do we have the same
problem?
We may need to use some Windows Installer Platform SDK tool to further
track the issue:

HOWTO: Use the Orca Database Editor to Edit Windows Installer Files
http://support.microsoft.com/?id=255905

We can use Orca to perfom an consistence check of the MSI generated.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Nov 20 '05 #5

P: n/a
Hi Simon,

How large is the MSI? If it is too large, we cannot attach it here. You may
also try turning on the verbose log of the installation, by running the
following command:

msiexec /i Setup1.msi /l*v c:\Setup1.log

Then we can find the log at "c:\Setup1.log". You may add the log to a zip
and attach it here. You may also analyze the log by yourself.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Nov 20 '05 #6

P: n/a
Hi Simon,

The component in question is "C__1D9076B37C67F487D94C095FCE0C5E2C". Do we
have it in the "Component" table? We can use Orca to search for the string
in the MSI generated. In addition, do we have the string in the "File"
table, "FeatureComponents" table, or other tables?

In addition, if we create a new setup project with exactly the same set of
files, do we have the problem? You may also try adding the MSI to a zip and
attaching it here. I am not sure whether that size is allowed or not.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Nov 20 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.