none
Error 2835: The control ErrorIcon was not found on dialog ErrorDialog

    Question

  • Hello, I am getting this error message only when running my setup.exe on certain computers.  This does not happen all of the time, and actually happens very infrequently.  This would leave one to believe it had to do with something environmental on the target system.  However, I cannot find anything wrong with the setup of the target system when I get this error message.  I will paste the pertinent areas of the verbose install log that I created to try to resolve this issue below:

     

    PublishFeatures: Feature: DefaultFeature
    Action 16:33:59: PublishProduct. Publishing product information
    1: _6FEFF9B68218417F98F549.exe
    1: _C30A7E0FA298213F3B9654.exe
    1: {1A055310-1166-492B-A0DA-5867BD3A948D}
    Action ended 16:33:59: InstallExecute. Return value 1.
    Action 16:33:59: RemoveExistingProducts. Removing applications
    Action start 16:33:59: RemoveExistingProducts.
    Action ended 16:33:59: RemoveExistingProducts. Return value 1.
    Action 16:33:59: InstallFinalize.
    Action start 16:33:59: InstallFinalize.
    Action 16:33:59: RollbackCleanup. Removing backup files
    DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDialog
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDialog,
    Error 1001. Error 1001. An exception occurred during the Commit phase of the installation. This exception will be ignored and installation will continue. However, the application might not function correctly after installation is complete. --> Value cannot be null.
    Parameter name: value
    MSI (s) (20!BC) [16:34:01:241]: ««朁䋆««««栗䋆⃰䋥«枸䋆ﶰ 䚌«䍗䋌ﶰ 䚀䍻䋌ﶰ «Ā
    DEBUG: Error 2769:  Custom Action _E20109A9_7B77_49A9_844C_6236DF868ECE.commit 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: _E20109A9_7B77_49A9_844C_6236DF868ECE.commit, 1,
    Action 16:34:01: Rollback. Rolling back action:
    Rollback: Publishing product information
    Rollback: Publishing Product Features
    Rollback: Publishing assembly information
    Rollback: Registering product
    Rollback: _DE448F58_C9EC_4AEE_994E_D2CD05DD06B1.install
    Rollback: _F40F9AA5_3590_49DC_82FC_5F9DB0B8E717.rollback
    Rollback: _E20109A9_7B77_49A9_844C_6236DF868ECE.commit
    Rollback: Creating shortcuts
    Rollback: Copying new files
    Rollback: Removing ODBC components
    Rollback: Updating component registration
    Action ended 16:34:01: InstallFinalize. Return value 3.
    Action ended 16:34:01: INSTALL. Return value 3.
    Property(S): UpgradeCode = {123FDF48-5ED4-4124-8777-15CF8AB13021}
    Property(S): _DE448F58_C9EC_4AEE_994E_D2CD05DD06B1.install = /installtype=notransaction /action=install /LogFile= /TDir="E:\Viewpoint Repository\\" "E:\Viewpoint Repository\LaunchServerSetup.dll" "C:\DOCUME~1\vcs\LOCALS~1\Temp\CFG32.tmp"
    Property(S): _F40F9AA5_3590_49DC_82FC_5F9DB0B8E717.rollback = /installtype=notransaction /action=rollback /LogFile= "E:\Viewpoint Repository\LaunchServerSetup.dll" "C:\DOCUME~1\vcs\LOCALS~1\Temp\CFG32.tmp"
    Property(S): _E20109A9_7B77_49A9_844C_6236DF868ECE.commit = /installtype=notransaction /action=commit /LogFile= /TDir="E:\Viewpoint Repository\\" "E:\Viewpoint Repository\LaunchServerSetup.dll" "C:\DOCUME~1\vcs\LOCALS~1\Temp\CFG32.tmp"
    Property(S): TARGETDIR = E:\Viewpoint Repository\
    Property(S): _3248AC317C904DB695819F3DEF10AB4A = E:\Viewpoint Repository\Viewpoint Remote Service Setup\
    Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
    Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start Menu\Programs\
    Property(S): _960EDFD7E0FB486EAC6DCDFF05B14CBC = C:\Documents and Settings\All Users\Start Menu\Programs\Viewpoint Construction Software\

     

    I cannot seem to figure out what is going wrong here, any help would be appreciated!

     

    Tim

    Thursday, October 16, 2008 6:03 PM

Answers

  • That 2835 is a minor whine about the Error dialog that's going to be shown, not the problem. The real issue is that:

     

    Custom Action _E20109A9_7B77_49A9_844C_6236DF868ECE.commit 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: _E20109A9_7B77_49A9_844C_6236DF868ECE.commit, 1,

    So do you have a Commit custom action? It sure looks like you do, and it's crashed.

     

    Thursday, October 16, 2008 9:31 PM
    Moderator

All replies

  • That 2835 is a minor whine about the Error dialog that's going to be shown, not the problem. The real issue is that:

     

    Custom Action _E20109A9_7B77_49A9_844C_6236DF868ECE.commit 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: _E20109A9_7B77_49A9_844C_6236DF868ECE.commit, 1,

    So do you have a Commit custom action? It sure looks like you do, and it's crashed.

     

    Thursday, October 16, 2008 9:31 PM
    Moderator
  • Thanks Phil.  Yes, I do have a Commit CA, but not sure what has gone wrong with it.  I will keep researching and may post again.  This has been very helpful.

     

    Tim

     

    Thursday, October 16, 2008 9:55 PM
  • Tim,

    Did you figure out what was going on with your Commit CA? I'm having a similar problem to the symptoms you describe above. Here's a snippet from my log:

    <LOGOUTPUT>
    MSI (s) (14:30) [08:21:46:816]: Executing op: CustomActionSchedule(Action=_E0F0AE34_8EE2_4A85_82B0_2CE22C5D13FD,ActionType=1042,Source=C:\Program Files\GOSE Simulation Builder\bin\simulationBuilderSetupCustomAction.exe,Target="C:\Program Files\GOSE Simulation Builder\<>1.6",)
    MSI (s) (14:30) [08:21:46:972]: Note: 1: 1721 2: _E0F0AE34_8EE2_4A85_82B0_2CE22C5D13FD 3: C:\Program Files\GOSE Simulation Builder\bin\simulationBuilderSetupCustomAction.exe 4: "C:\Program Files\GOSE Simulation Builder\<>1.6"
    MSI (s) (14:30) [08:21:46:972]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (34:D4) [08:21:46:987]: Note: 1: 2262 2: Error 3: -2147287038
    DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDialog
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDialog,
    Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: _E0F0AE34_8EE2_4A85_82B0_2CE22C5D13FD, location: C:\Program Files\GOSE Simulation Builder\bin\simulationBuilderSetupCustomAction.exe, command: "C:\Program Files\GOSE Simulation Builder\<>1.6"
    MSI (s) (14:30) [08:21:49:140]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (14:30) [08:21:49:140]: Product: GOSE Simulation Builder 0.3.3 -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: _E0F0AE34_8EE2_4A85_82B0_2CE22C5D13FD, location: C:\Program Files\GOSE Simulation Builder\bin\simulationBuilderSetupCustomAction.exe, command: "C:\Program Files\GOSE Simulation Builder\<>1.6"
    </LOGOUTPUT>

    I'm not able to glean anything useful from this, though.

    Thanks,
    Stephen

     

    Tuesday, June 2, 2009 1:52 PM
  • If you're running a custom action that fires off another setup that is MSI-based it won't work. Recursive MSI installs are not allowed, just in case that's what you're doing.
    Unfortunately code failures like this are often based on the assumption that because it works when you run it by itself then it will also just work when run as a custom action. Being careful to check the results of each method call, catching exceptions, and checking for null objects and so on will tell you where it's going wrong.
    Phil Wilson
    Tuesday, June 2, 2009 9:18 PM
    Moderator
  • I'm getting nearly the same thing.
    When I try to uninstall I get this error:
    "Error 1001 ....value cannot be null...Parameter name: path1".

    There is no path1 parameter in my custom action.
    I'm unable to uninstall my app. I've tried commenting out and then rebuilding the Custom Action and Setup but to no avail, the installer apears to either ignore my new .msi and use the original or something else besides my Custom Action is at fault here.
    The error log is no of much help.
    What about the InstallState file is this of an use, could there be some paramaters in there that are at fault?

    I'm finding it very difficult to get a clear description of how the Windows Installer works, what is the InstallState file for?  Does the windows installer store the oringinal msi somewhere for the uninstall or repair purposes? If I override the msi and then uninstall should it still work?


    http://learnerps-dotnet.blogspot.com/
    Tuesday, August 4, 2009 10:07 AM
  • Being strict here, the installstate file is nothing to do with Windows Installer. It's an implementation detail of the way Visual Studio adds a setup framework for calling installer classes. Between Windows Installer and the installer class is a C++ Dll that loads a .NET framework, locates your assembly, reflects on it, finds installer classes, instantiates them, calls methods, locates installstate etc. The inner workings of all this are a black box, and failures tend to be tough to diagnose as you've discovered. If you know C++, a plain C++ Dll call is a much simpler interface. There's also no advantage to an Installer class compared to just running a .NET program.

    The uninstall doesn't use you updated MSI file after you rebuild it. That can't work because your rebuilt MSI might be nothing like what you've installed already - it may have different files and so on. The uninstall uses a cached version of the MSI file to do the uninstall, stored in Windows\installer. If you could identify the cached MSI file in that folder, edit it with Orca, identify your uninstall custom action in the InstallExecuteSequence and set its condition to 0 then it will not call it at unstall time.

    I recommend you get hold of Virtual PC, Virtual Server, Hyper-V or some virtualization scheme so you test this on a virtual machine, and if it fails then you just revert to the base VM and start again. VMs are perfect for this situation.
    Phil Wilson
    Friday, August 7, 2009 6:42 PM
    Moderator

  • Hi Phil,
    Thanks again for clearing up some of the queries. 
    The uninstall doesn't use you updated MSI file after you rebuild it. That can't work because your rebuilt MSI might be nothing like what you've installed already - it may have different files and so on. The uninstall uses a cached version of the MSI file to do the uninstall, stored in Windows\installer. If you could identify the cached MSI file in that folder, edit it with Orca, identify your uninstall custom action in the InstallExecuteSequence and set its condition to 0 then it will not call it at unstall time. 

    I found the cached version, the InstalledState file had informatin on the location. 
    I fixed my problem by dropping in a  working Custom Action Dll into my installation target directory. The error I was getting was because my Custom Action had a bug, I fixed it, dropped the new version into my Program Files and worked fine. So I guess the msi is stored in a cached location but the Custom Action implementation is actually stored in the target location, that's why you see the <customaction>.dll in you target installation directory.

    I recommend you get hold of Virtual PC, Virtual Server, Hyper-V or some virtualization scheme so you test this on a virtual machine, and if it fails then you just revert to the base VM and start again. VMs are perfect for this situation.
    Phil Wilson
    Yes the Virtual PC is the answer, unfortunately the one I was using didn't have the Undo Disk setting set so I couldn''t reverse the installation.

    http://learnerps-dotnet.blogspot.com/
    Tuesday, August 18, 2009 8:20 AM