none
Error 2869 with Windows XP

    Question

  • Moved from http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/798f637a-b15e-4dc7-9f24-c0cb3fe57893 
     
    Some our customers receiving  error 2869 during the installation on Windows XP Professional SP2. MSI runs Custom Actions that uses .Net dll that invokes web service.
     Users are administrators and PC connected to the internet. Customer was asked to try again with a log option :
    msiexec.exe /i <path to msi> /L*v c:\logfile.txt
    and ... installation succeeded. Log contains some errors about window boundaries and other meaningless junk...
    Is there a chance that  there is somehow uncaught .Net exception within custom action code , that happens very seldom and therefore sometimes installation  doesn't succeeds?

    I don't have a clue now... Does anybody get with this issue too?

    Best regards,
    Michael
    Sunday, January 18, 2009 7:19 AM

Answers

  • If you get a log of when it fails, post it. 2869 is a downstream error about the error dialog that it's about to show, not the actual error, and unfortunately it hides the real error.  So you might get lots of people who have had "the famous 2869 error" but the actual error that causes the problem is something else, and most commonly a custom action failure. If you have a log with errors then post it, it might be useful. We can see if they are associated with your custom action. 
    Phil Wilson
    • Marked as answer by Kira Qian Friday, January 23, 2009 4:01 AM
    Monday, January 19, 2009 7:22 PM
    Moderator

All replies

  • If you get a log of when it fails, post it. 2869 is a downstream error about the error dialog that it's about to show, not the actual error, and unfortunately it hides the real error.  So you might get lots of people who have had "the famous 2869 error" but the actual error that causes the problem is something else, and most commonly a custom action failure. If you have a log with errors then post it, it might be useful. We can see if they are associated with your custom action. 
    Phil Wilson
    • Marked as answer by Kira Qian Friday, January 23, 2009 4:01 AM
    Monday, January 19, 2009 7:22 PM
    Moderator
  • Unfortunately, it's pretty hard to reproduce this- sometimes second try of installation of the same product succeeds (according to customer's feedback). I'll post the log as soon as it will be available
    Tuesday, January 20, 2009 7:51 AM
  •  

    Finally,  I've got  the log from another customer with the same problem on XP. Unfortunatelly, I can't post it here - somehow it's  too large (over the chars limit that this blog engine support). I've uploaded it here: http://rapidshare.com/files/189743418/logfile.txt.html 

    Any help will be appreciated.

     

    Monday, January 26, 2009 4:47 PM
  • Phil, I'm having a similar problem. I think I've found the problem in the error log but I'm having a hard time understanding what's going on. Can you help? Below is the sectin where the error occurs:

    MSI (s) (40:60) [08:38:30:233]: Executing op: CustomActionSchedule(Action=_A5833F29_6EEC_4241_AB4C_536FE8F42861.rollback,ActionType=1281,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=rollback /LogFile= "C:\Program Files\Compunetix Inc\CONTEX SUMMIT Access Server 2\AccessServerGUI.exe" "C:\DOCUME~1\jwebb\LOCALS~1\Temp\CFG572.tmp")

    MSI (s) (40:60) [08:38:30:233]: Executing op: ActionStart(Name=_253BD91D_52FC_434F_92EB_163FE7EA6B63.install,,)

    Action 8:38:30: _253BD91D_52FC_434F_92EB_163FE7EA6B63.install.

    MSI (s) (40:60) [08:38:30:233]: Executing op: CustomActionSchedule(Action=_253BD91D_52FC_434F_92EB_163FE7EA6B63.install,ActionType=1025,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=install /LogFile= "C:\Program Files\Compunetix Inc\CONTEX SUMMIT Access Server 2\AccessServerGUI.exe" "C:\DOCUME~1\jwebb\LOCALS~1\Temp\CFG572.tmp")

    MSI (s) (40:7C) [08:38:30:248]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI57B.tmp, Entrypoint: ManagedInstall

    MSI (s) (40!38) [08:38:30:529]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (c) (9C:2C) [08:38:30:529]: Note: 1: 2262 2: Error 3: -2147287038

    DEBUG: Error 2869:  The dialog ErrorDialog has the error style bit set, but is not an error dialog

    MSI (c) (9C:2C) [08:38:30:545]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg


    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2869. The arguments are: ErrorDialog, ,

    MSI (c) (9C:2C) [08:39:09:224]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (c) (9C:2C) [08:39:09:224]: Product: CONTEX SUMMIT Access Server 2 -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2869. The arguments are: ErrorDialog, ,

     

    Error 1001.

    MSI (s) (40!38) [08:39:09:224]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (s) (40!38) [08:39:09:224]: ¥¥朁㿟¥¥¥¥栗㿟⃰㿾¥枸㿟̠
    ¥䍗㿥̠
    䍻㿥̠¥Ā

    MSI (s) (40:7C) [08:39:09:224]: Leaked MSIHANDLE (53) of type 790531 for thread 3640

    MSI (s) (40:7C) [08:39:09:224]: Note: 1: 2769 2: _253BD91D_52FC_434F_92EB_163FE7EA6B63.install 3: 1

    MSI (s) (40:7C) [08:39:09:224]: Note: 1: 2262 2: Error 3: -2147287038

    DEBUG: Error 2769:  Custom Action _253BD91D_52FC_434F_92EB_163FE7EA6B63.install did not close 1 MSIHANDLEs.

    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. The arguments are: _253BD91D_52FC_434F_92EB_163FE7EA6B63.install, 1,

    Action ended 8:39:09: InstallFinalize. Return value 3.

    MSI (s) (40:60) [08:39:09:239]: User policy value 'DisableRollback' is 0

    MSI (s) (40:60) [08:39:09:239]: Machine policy value 'DisableRollback' is 0

    MSI (s) (40:60) [08:39:09:239]: Executing op: Header(Signature=1397708873,Version=405,Timestamp=1028998346,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)

    I can provide the complete log if necessary -- it is 922 KB -- let me know if you want to take a look.

    Any help will be appreciated.

    Thursday, October 21, 2010 12:49 PM
  • That's your install custom action. I'll say it again - it's nearly always a custom action that causes errors. That _253BD91D_52FC_434F_92EB_163FE7EA6B63.install is how Visual Studio names custom actions, and Target=ManagedInstall,CustomActionData=/installtype tells me it's managed code.

    The essential thing about running code where it's nearly impossible to debug it to write it very defensively, assume anything can fail, trace to a text file if possible. You're running code in an msiexec.exe process, not an interactive user process.  


    Phil Wilson
    Thursday, October 21, 2010 9:46 PM
    Moderator