Hello,
I'm currently evaluating InstallAware and when i'm running a test install i get an error: "Error - The installer has encountered an unexpected error installing this package. This may indicate a problem with the package. The Error Code is 2709." I can't find out what this error means, so i hope you guys can.
Best regards,
Michiel
Error code 2709
Michiel,
I could find some google references to 2709 but nothing that pokes me in the eye as the probable cause. When you say you are evaluating does that mean you've assembled a major league setup from scratch or have you something reproducible as a small project? If your project is small enough to email (including files) and there's nothing confidential in your project that you can't make publicly available, PM me and I'll give you my email address you can send it to. I'll be happy to try and build it independently and see if I can find something in particular.
Edit: I just noticed that PM'ing is disabled on the board. It used to work so maybe it's my settings but I can't find anything in my profile. Is it just me, or is it a universal block?
I could find some google references to 2709 but nothing that pokes me in the eye as the probable cause. When you say you are evaluating does that mean you've assembled a major league setup from scratch or have you something reproducible as a small project? If your project is small enough to email (including files) and there's nothing confidential in your project that you can't make publicly available, PM me and I'll give you my email address you can send it to. I'll be happy to try and build it independently and see if I can find something in particular.
Edit: I just noticed that PM'ing is disabled on the board. It used to work so maybe it's my settings but I can't find anything in my profile. Is it just me, or is it a universal block?
Peter. Smartly dressed, he still resembles an unmade bed.
InstallAware MVP
InstallAware MVP
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Unfortunately, we have had to disable PMs to combat spam.
@GW44: Keep your posts on topic, idle speculation or rants are not tolerated on these public InstallAware forums. Consider this your one and only public warning before being banned.
@Michiel: If you had read the PLEASE READ BEFORE POSTING sticky you would have seen that among many other things there is a recommendation to search the forums. People have posted here asking about MSI error codes and we don't see the point in repeating the same answers over and over again when they have been previously documented.
@GW44: Keep your posts on topic, idle speculation or rants are not tolerated on these public InstallAware forums. Consider this your one and only public warning before being banned.
@Michiel: If you had read the PLEASE READ BEFORE POSTING sticky you would have seen that among many other things there is a recommendation to search the forums. People have posted here asking about MSI error codes and we don't see the point in repeating the same answers over and over again when they have been previously documented.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Michiel,
It's been my experience in the past that where I've encountered spooky runtime errors it's because the project file was somewhat top-heavy. I'm not suggesting that 25,000 files should be a problem but that's what I've observed in some big projects. I get the impression that you did not manually add the files one-by-one,
, but they are added in response to a folder pickup of all files? If so, what happens if you cut it down to a handful of files? That might eliminate the msi tables getting saturated but that's only a wild guess for the most part.
Another thing to try is to comment out some of the code that does the accessory installation stuff like installing PHP on IIS. I'd like to think that it might be one small piece of code that tips it into the dumpster. IA is actually very solid in preventing runtime errors getting thrown but it's still subject to whatever Windows msi decides to do. I used to get lots of errors thrown up when I used InstallShield and in all cases it was one small thing that tripped it up. That might be the case in your project but that's speculation from my view at left field.
I guess it's a bit like coding. Too many changes can make it difficult to know which one caused a problem. Hope this helps some of the way. Good luck!
It's been my experience in the past that where I've encountered spooky runtime errors it's because the project file was somewhat top-heavy. I'm not suggesting that 25,000 files should be a problem but that's what I've observed in some big projects. I get the impression that you did not manually add the files one-by-one,
, but they are added in response to a folder pickup of all files? If so, what happens if you cut it down to a handful of files? That might eliminate the msi tables getting saturated but that's only a wild guess for the most part.Another thing to try is to comment out some of the code that does the accessory installation stuff like installing PHP on IIS. I'd like to think that it might be one small piece of code that tips it into the dumpster. IA is actually very solid in preventing runtime errors getting thrown but it's still subject to whatever Windows msi decides to do. I used to get lots of errors thrown up when I used InstallShield and in all cases it was one small thing that tripped it up. That might be the case in your project but that's speculation from my view at left field.
I guess it's a bit like coding. Too many changes can make it difficult to know which one caused a problem. Hope this helps some of the way. Good luck!
Peter. Smartly dressed, he still resembles an unmade bed.
InstallAware MVP
InstallAware MVP