[Solved] WinToolkit Installer - intsalling office fails

Etz · March 17, 2014

2. Yep it should work, don't see why not. You can have your installs/drivers/updates anything as long as you specified the correct places in the ini.

Well, I dont seem to quite understand. (Must have been long day, so I apologise)

If I dont edit Install.ini would it still work or I explictly have to change INSTALLDIR in there if I add Installer via AIO tool or it would just work by default?

PS: Connectivity issue resolved by itself, but still thx for the tip, I already tried that didnt help much

Legolash2o · March 17, 2014

If you add an install via AIO then you don't need to touch the install.ini. You can move the files as long as you specified the new location within the install.ini.

Basically the install.ini adds a list of locations to a list which already contains 2 locations by default. When it comes to your install entry it will just scan all the directories until it finds a match.

foreach (installlocation in list)

{

if (setup exists in this directory)

-{then install}

else

-{keep checking the other directories.}

}

Etz · March 17, 2014

Well, thx...now Its clear as glass

Edited March 17, 2014 by Etz

Etz · March 20, 2014

Hmm...for a some strange reason, it started to fail again with 1.4.34.14 (Didnt manage to test on 1.4.34.13), as it looks like, it adds trailing slash to the syntax for some strange reason.. :g:

Syntax used:

Syntax from registry:

|%DVD%:\WinToolkit_Apps\Office_2013_Professional\Setup.exe*/configure %APP%\Setup.xml

Office Installer log output:

Timestamp    Process    TID    Area    Category    EventID    Level    Message    Correlation03/20/2014 21:28:45.503    SETUP (0x74c)    0x990        Click-To-Run    aqkhc    Medium    CmdLine:"D:\WinToolkit_Apps\Office_2013_Professional\Setup.exe" /configure D:\WinToolkit_Apps\Office_2013_Professional\Setup.xml\    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run Telemetry    aqkhd    Medium    {"SessionID":"79e7ef88-bf61-45f5-94e8-615a33301b3b","GeoID":"70","Ver":"15.0.4595.1000","Bitness":"32","IntegrityLevel":"0x3000","SecuritySessionId":"1"}    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run Telemetry    aqkhe    Medium    {"SessionID":"79e7ef88-bf61-45f5-94e8-615a33301b3b","GeoID":"70","Ver":"15.0.4595.1000","OSVersion":"6.2","SP":"0","ProductType":"1","ProcessorArch":"9","Locale":"1061"}    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    amawz    Medium    Args::ParseArgument: Parsing commandline.    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    ambpm    Medium    Args::Load: Have Admin scenario    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    amaw0    Medium    Args::GetNextArgument: Next argument: /configure    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    amaw0    Medium    Args::GetNextArgument: Next argument: D:\WinToolkit_Apps\Office_2013_Professional\Setup.xml\    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    aoh7y    Medium    Args::GetConfigFile: config file: D:\WinToolkit_Apps\Office_2013_Professional\Setup.xml\    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    appfq    Medium    Args::Load: product release id: none  culture: en-us    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    apvr9    Medium    TrySetUserRegistry::TrySetAttemptGetKey: Setting Attempt Get Key for none    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    amaw8    Medium    TrySetUserRegistry::TrySetLicenseTokenOrKey: No key or token found for none    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    aoh76    Medium    HandleCommandLineAction::HandleStateAction: Not OOD scenario nor showing ODT help, check for elevation.    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    aoh8l    Medium    TryGetElevation::HandleStateAction: Already running from elevated context.    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    aoh78    Medium    HandleCommandLineAction::HandleStateAction: Starting Admin tool scenario.    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    aoh8d    Medium    HandleCommandLineAction::HandleStateAction: Start installation with configuration file: D:\WinToolkit_Apps\Office_2013_Professional\Setup.xml\    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    anwv3    Medium    Configuration::InitializeDefaults: Base URL is http://officecdn.microsoft.com/pr/39168D7E-077B-48E7-872C-B232C3E72675    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    anwv1    Medium    Configuration::Load: Using the default values. No config file supplied.    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    aodb1    Medium    Configuration::AdjustBaseUrlForLocalSource: Found the version cab at: D:\WinToolkit_Apps\Office_2013_Professional\Office\Data\v32.cab    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    apm49    Medium    Configuration::AdjustBaseUrlForLocalSource: Removing \Office\Data    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    aodb0    Medium    Configuration::Load: Adjusted base url for local source: D:\WinToolkit_Apps\Office_2013_Professional    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    aqto1    Medium    BaseConfigure::TryGetConfiguration: Base Url D:\WinToolkit_Apps\Office_2013_Professional is of type DVD    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    ambbf    Medium    AdminConfigure::HandleStateAction: No product changes. Configuring an Update settings scenario.    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    ambbg    Medium    ConfigureUpdatesSettings::HandleStateAction: Installation path is: C:\Program Files\Microsoft Office 15\ClientX64    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    ambbl    Unexpected    ConfigureUpdatesSettings::HandleStateAction: OException has occured while trying to launch uninstallation UnexpectedError (ConfigureUpdatesSettings::HandleStateAction Unable to find a client installed at: C:\Program Files\Microsoft Office 15\ClientX64).    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    aoh71    Medium    BootstrapperState::OnError: Error has occured. Go to ExitBootStateMachine.    03/20/2014 21:28:45.519    SETUP (0x74c)    0x990        Click-To-Run    aoh9f    Medium    BootStateMachine::ShowFailureUI: Showing failure UI.    03/20/2014 21:41:15.269    SETUP (0x74c)    0x990        Click-To-Run    aoh72    Medium    ExitBootStateMachine::HandleStateAction: Bootstrapper workflow exiting with result: 0x0    03/20/2014 21:41:15.269    SETUP (0x74c)    0x990        Click-To-Run    aoh9z    Medium    AdminBootstrapper::Main: Installation came back with -2147418113.    03/20/2014 21:41:15.269    SETUP (0x74c)    0x990        Logging Liblet    aqc99    Medium    Logging liblet uninitializing.

Notice, the trailing slash, which transforms Setup.xml to a directory (leaving "config file" undefined) and of course as a result It just fails again...

Edited March 20, 2014 by Etz

Legolash2o · March 20, 2014

Hmm, I will look into that right now, then I've got to write you guys an article

Legolash2o · March 20, 2014

Oh damn, you're right! I think it's adding it onto everything!

EDIT: IT adding it to everything you add via AIO-Integrator but not install.ini, fixing it now!

Etz · March 20, 2014

Most installers dont have a so detailed log, fortunately Office Click-to-run installer has, check the first line, it even logs syntax that you actually used to execute Setup.exe

Makes script debugging pretty easy, heh..

Edited March 20, 2014 by Etz

Legolash2o · March 20, 2014

Fixed, in the latest test build

Etz · March 20, 2014

Hmm...now this looks odd...

It looks like it ran Setup.exe twice, according to logs, install itself succeeded though.

Anyway, will try to figure out what exactly went wrong, it shouldnt display any dialogs (and usually dont, no cmd window, no nothing that is why this XML is primarily used)

Edited March 20, 2014 by Etz

Legolash2o · March 20, 2014

I can fix that, make sure you dont have it in both install.ini and registry. You may have integrated a few times into the same image

Etz · March 20, 2014

I am pretty sure I havent integrated it multiple times as I always start testing with untouched copy

And I dont use install.ini (well at least so far).

Anyway will build new one from scratch tomorrow (khmm...technically today) evening, but now...off to bed

I may have mixed something and used old sourcedir, but its easy to figure out, there should be 2 entries in the registry then?

Will mount registry and check whats in there, will let you know (takes couple of minutes), as it indeed runs twice.

EDIT: Registry at least has only one entry present... :g:

Anyway as I really may have mixed things up and used already processed source, I will try again at the evening.

To be sure I just deleted that directory, so no more mixups are possible

Edited March 20, 2014 by Etz

Legolash2o · March 20, 2014

Thanks, much appreciated. I've already uploaded a new test version removing the console window and other fixes to the main Win Toolkit exe.

Etz · March 21, 2014

No worries, as I always try to use youre "cutting edge" releases as I build Images solely only for my own personal purpose.

If no one would use those, and report any possible hiccups, there would be no evolution and stable versions aswell...

Edited March 21, 2014 by Etz

Etz · March 21, 2014

Built image from scratch, and still no joy...

No CMD window, but install failed.

Now it wrapped syntax between " marks.

03/21/2014 22:31:15.965    SETUP (0xb98)    0xb6c        Click-To-Run    aqkhc    Medium    CmdLine:"D:\WinToolkit_Apps\Office_2013_Professional\Setup.exe" "/configure D:\WinToolkit_Apps\Office_2013_Professional\Setup.xml"

As a result install failed:

03/21/2014 22:31:15.965    SETUP (0xb98)    0xb6c        Click-To-Run    aoh8e    Monitorable    HandleCommandLineAction::HandleStateAction: Invalid Admin command. Command: "/configure D:\WinToolkit_Apps\Office_2013_Professional\Setup.xml"

Used latest stable 1.4.35

Edited March 21, 2014 by Etz

Legolash2o · March 21, 2014

Already fixed in v1.4.36.1

Etz · March 21, 2014

Damn...I cannot test as fast as you can release

Etz · March 22, 2014

Sucess! :dancing:

But now I already know that I have to remaster my image and try again:

http://www.wincert.net/forum/topic/12077-some-problems-with-the-new-wintoolkit-installer/?p=106043

And I have to test Visual Studio 2013 XML anyway...

Edited March 22, 2014 by Etz

Etz · March 22, 2014

Re-tested with latest stable: 1.4.36.2, still works like a charm.

I really owe you Lego, as this has been a real PITA for you to get this work properly.

But as there are lots of other installers also, which use similar method for tweaking and customizing the Setup process, I think lot of users will actually benefit from this

Edited March 22, 2014 by Etz

Sign In

[Solved] WinToolkit Installer - intsalling office fails

Recommended Posts

Etz

Legolash2o

Etz

Etz

Legolash2o

Legolash2o

Etz

Legolash2o

Etz

Legolash2o

Etz

Legolash2o

Etz

Etz

Legolash2o

Etz

Etz

Etz

Join the conversation

Browse

Activity