Doinstall Error Code
Contents |
install Starred by 2 users Reported by n...@semenkovich.com, Sep 4 2014 Back to list Status: WontFix google chrome error 1722 Owner: ---- Closed: Oct 2015 Cc: grt@chromium.org, nyerramilli@chromium.org, robertshield@chromium.org, wfh@chromium.org, gab@chromium.org,
Google Chrome Msi There Is A Problem With This Windows Installer Package
ranjitkan@chromium.org Components: Enterprise Internals>Installer OS: Windows Pri: 2 Type: Bug Enterprise-Triaged Via-Wizard chrome enterprise MSI Sign in to add a comment UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2138.3 Safari/537.36 Steps to reproduce the problem: The provided Chrome google chrome cleanup tool 64-bit enterprise MSI won't install (googlechromestandaloneenterprise64.msi). This is over a pre-existing MSI install of the 32-bit version. The UI displays: """ Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. """ What is the expected behavior? What went wrong? Full MSI log attached. Excerpt of the failure: CustomAction DoInstall returned actual error code -2147219198 (note this may not be 100% accurate if translation happened inside sandbox)^M MSI (s) (8C:5C) [20:16:19:358]: Note: 1: 1722 2: DoInstall 3: C:\WINDOWS\Installer\MSI6045.tmp 4: /silent /install "appguid={8A69D345-D564-463c-AFF1-A69D9E530F96}&appname=Google Chrome&needsAdmin=True&brand=GGRV&ap=x64-stable" /installsource enterprisemsi /appargs "appguid={8\ A69D345-D564-463c-AFF1-A69D9E530F96}&installerdata=%7B%22distribution%22%3A%7B%22msi%22%3Atrue%2C%22system_level%22%3Atrue%2C%22verbose_logging%22%3Atrue%7D%7D" ^M MSI (s) (8C:5C) [20:16:19:358]: Note: 1: 2205 2: 3: Error ^M MSI (s) (8C:5C) [20:16:19:358]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1722 ^M MSI (c) (84:80) [20:16:19:387]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg ^M Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action DoInstall, location: C:\WINDOWS\Installer\MSI6045.tmp, command: /silent /install "appgu\ id={8A69D345-D564-463c-AFF1-A69D9E530F96}&appname=Google Chrome&needsAdmin=True&brand=GGRV&ap=x64-stable" /installsource enterprisemsi /appargs "appguid={8A69D345-D564-463c-AFF1-A69D9E530F96}&installerdata=%7B%22distribution%22%3A%7B%22msi%22%3Atrue%2C%22system_level%22%3Atru\ e%2C%2
zetron01-06-2003, 07:34 PMBoth master and child setups were built by IS Pro 7 SP 1. When the child setup completed, an error code -2147024864 was returned. Everything supposed to be installed by https://bugs.chromium.org/p/chromium/issues/detail?id=410648 the child setup was installed successfully. The child setup image was put in a file group. Its target was set to
11:19 AMIn my install kit I http://helpnet.installshield.com/installshield19helplib/Subsystems/installshield19langref/helplibrary/LangrefDoInstall.htm am trying to launch a child install kit using the Doinstall function. This works on some machines (Including my dev environment) but not on other machines! google chrome On the machines it fails on the Doinstall function. It returns an error number which corresponds to an Access Denied error. It seem to be a problem with the iscript.dll Does anybody know doinstall error code how to solve the problem? Jippy-02-27-2002, 11:43 AMThat's odd.... To quote the InstallShield Help guide: The setup launched by DoInstall must have been created with the same major version, minor version, and build number of InstallShield as the setup that is launching it. Attempts to use DoInstall to launch a setup created with any other version of InstallShield may not be successful. Are your setups build in the same version? Also, does it work if you try the LaunchApp or LaunchAppAndWait functions? =-Jason Powered by vBulletin Version 4.2.2 Copyright © 2016 vBulletin Solutions, Inc. All rights reserved.
another InstallShield installation that has a valid setup executable file (.exe). The second installation is executed immediately when this function is called. The third parameter, nOptions, specifies various options, including whether the installation should wait until the launched application terminates before continuing. Note: DoInstall cannot be used directly to launch a .msi file. In addition, because DoInstall adds command-line parameters that are specific to InstallShield installations, DoInstall should not be used to launch a non-InstallShield installation. To launch a non-InstallShield installation, use the LaunchAppllication function. Syntax DoInstall ( byval string szSetupExe, byval string szCmdLine, byval number nOptions ); Parameters DoInstall Parameters Parameter Description szSetupExe Specifies the fully qualified name—including a drive designation and complete path—of the setup executable file to be launched. Alternatively, you can specify the compiled script file of the installation to be launched. For InstallScript MSI installations, you can specify the installation's .msi package. Note that in order to be able to use DoInstall, your installation must include a valid setup executable file named Setup.exe, or an alternative name, as described in Additional Information. szCmdLine Specifies the command line for the launched installation. You can specify any valid startup InstallShield command line for this parameter. Note that DoInstall automatically adds some command-line switches, depending on the nOptions specified. Note: Unlike with previous versions of InstallShield, if you are passing command-line parameters to a child InstallScript MSI installation, you must pass these options through the /z parameter (as when launching the installation directly). nOptions Specifies options for launching the installation. You can specify any valid LaunchApplication option, including: • LAAW_OPTION_NOWAIT • LAAW_OPTION_WAIT You can also specify some additional options that apply only to DoInstall: • DOINSTALL_OPTION_NOHIDEPROGRESS—Specifies that the entire initialization user interface, including the initial progress dialog and splash screen (if any), should be displayed for the child installation. If this option is not specified, DoInstall automatically hides the initialization user interface of the child installation by using the /hide_progress o