共用方式為

Windows Installer fails on Vista with 2869 error code.

  • 發行項

Omar had a problem: he was using VS 2005 SP1 on Vista to build his Windows Installer setup package for VSTO Outlook Add-In. When he tried to install the package - it was always failing with code 2869. He contacted me with "what is the deal?", I tracked more folks in VS Setup team and finally got to the bottom of the problem.

His setup has a custom action "SetSecurity" written in managed code (this is because he was following the deployment articles as indicated here). This custom action, which modifies CAS policy, threw the exception but the actuall exception message was never shown to the end user. Since one could not see the actual erro - troubleshooting the CA was nearly impossible.

So, how can you make your Windows Installer show the error messages displayed by the Custom Actions? You would need to manually modify Errors table in the MSI file (use Orca tool to do that) and add the following entry to it - 1001 "Error [1]: [2]" . Additional bonus to the guys who can make it happen automatically as the post build step J

Finally, I should notice that you would not need to do that when final VS 2005 Sercice Pack for Vista comes out.

[Update 3/9/07: Omar posted his side of the story and he also tells how to do the workaround automatically]

Comments

  • Anonymous
    March 02, 2007
    PingBack from http://cheatcodedirect.com/windows-installer-fails-on-vista-with-2869-error-code/

  • Anonymous
    March 04, 2007
    Misha, Thanks for the solution. When can we expect to have this issue fixed? Kind regards, Dennis

  • Anonymous
    March 09, 2007
    I just talked to the guys from the setup team and the issue will not be solved for Visual Studio 2005 - only for the next release codenamed "Orca". But please see Omar's blog (http://www.shahine.com/omar/VSTOAddinsAndVista.aspx) how to automate this workaround.

  • Anonymous
    March 10, 2007
    Thanks Misha and I have already tested the suggestion workaround with good outcome :-) Kind regards, Dennis

  • Anonymous
    May 14, 2007
    This soultion works for me on vista - 32 bit. For some reason, this doesn't work for me on x64. Any insight? regards, Yogesh

  • Anonymous
    May 31, 2007
    I'm trying to deploy a VSTO 2005 Outlook Add-In. My add in includes Custom Configuration Sections in the App.config file. If I deploy my add in without the custom configuration section functionality it behaves as expected; however when the custom configuration section was included it stopped working. Any insight?

  • Anonymous
    June 27, 2007
    Hello, I have the same problem with already compiled comercial program SYNCING.NET but I'm not a developer so I can't fix it and I would really like to use it on my Vista. So is there a way for me to somehow install this product on my computer? Thanks for the help!

  • Anonymous
    July 03, 2007
    The other way to deal with this problem for those who are not developers. Disable User Account Control in Windows Vista. A number of ways to do this can be found at http://www.petri.co.il/disable_uac_in_windows_vista.htm Then run the installer. If everything's OK, you should be able to install the application successfully. Do not forget to enable User Account Control after you install the application (for security reasons). I hope this will be useful. Thank you, Misha, for the solution for developers. Best regards, Jonas

  • Anonymous
    September 05, 2007
    The comment has been removed

  • Anonymous
    January 27, 2008
    Thanks Steffen! your script saved a lot work for me.

  • Anonymous
    June 30, 2008
    A quick fix to help troubleshoot error 2869 when installing the VBUC 2.0.

  • Anonymous
    October 07, 2008
    very easy solution was posted on Paulo Reichert's Blog http://blogs.conchango.com/pauloreichert/archive/2006/11/21/Windows-Installer-MSI-packages-error-code-2869-on-Windows-Vista.aspx "...The quick and dirty solution I found to make them install is to create a batch file with the following command: msiexec /i "path-to-package.msi" Save the file then right-click it and select "Run as Administrator". That makes it work. ..."

  • Anonymous
    June 05, 2009
    Quick solution: Right click on "setup.exe" file and select "Run as Administrator".

  • Anonymous
    July 20, 2009
    >> Gustavo said: >>Quick solution: Right click on "setup.exe" file and >>select "Run as Administrator". may i know is this really work without using "msiexec"?

  • Anonymous
    July 22, 2009
    Some helper would be appreciated... similar problem on Windows Server 2008.... I have an MSI package that has a bunch of custom actions included with it. I applied the NoImpersonate and also the error message fix mentioned here to the MSI and that got it working under Windows Vista. My issue now is, the same MSI installer just hangs on Windows Server 2008 64-bit (no error messages at all, not even the 2869 error message). It doesn't seem like the error message fix I applied from here is giving me any feedback during the hang. Are there any other special properties that need set in an MSI for Windows Server 2008 64-bit? Anyone else seen this problem? I have read that invoking a 64-bit program from a 32-bit application can cause a hang but that doesn't seem to be the case in my custom actions. Chris

  • Anonymous
    October 06, 2011
    Misha saves the day again