locked
Office 2016 (Volume Licencing Installer & ODT) RRS feed

  • Question

  • Hello, I am currently having issues installing Office 2016 with MDT using the ODT.

    I get the following errors.

    returned an unexpected return code: 110

    returned an unexpected return code: 30088

    I am also using an MSP file in the update folder just FYI this runs with no issue when clicking on Setup.exe manually.


    Alex Olver


    • Edited by brimanyo Wednesday, January 13, 2016 4:07 AM
    Wednesday, January 13, 2016 3:37 AM

All replies

  • Post BDD.log to something like OneDrive and share the link here.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Wednesday, January 13, 2016 4:28 AM
  • https://dl.dropboxusercontent.com/u/56669388/BDD.LOG


    Alex Olver

    Wednesday, January 13, 2016 4:31 AM
  • Have you checked the Office install logs generated in %tmp%?  I don't see anything in the MDT logs.  Also are you using a configuration.xml file? https://technet.microsoft.com/en-us/library/gg998766.aspx


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.



    • Edited by Ty Glander Wednesday, January 13, 2016 11:17 PM
    Wednesday, January 13, 2016 10:38 PM
  • So on the actual machine? Can you be more specific on the location?

    Alex Olver

    Thursday, January 14, 2016 9:32 PM
    • Edited by oriooff Thursday, January 14, 2016 10:15 PM
    Thursday, January 14, 2016 10:15 PM
  • Yea I know how to get MDT log files just wondering where the Office logs files are.

    Alex Olver

    Thursday, January 14, 2016 10:31 PM
  • Have you checked the Office install logs generated in %tmp%? 

    It would have to be on the machine that failed.


    • Edited by Ty Glander Thursday, January 14, 2016 10:50 PM
    Thursday, January 14, 2016 10:49 PM
  • Yes this is what I am asking can you tell me where those log files are in the %tmp% directory and what they might be called?!

    Alex Olver


    • Edited by brimanyo Friday, January 15, 2016 12:02 AM
    Thursday, January 14, 2016 11:59 PM
  • I can't tell if you are toying with me...

    either system temp: C:\Windows\Temp

    or the user temp: start->run->%tmp% and hit enter (it will be something like c:\users\Administrator\Appdata\Local\Temp


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.


    • Edited by Ty Glander Friday, January 15, 2016 12:07 AM
    Friday, January 15, 2016 12:04 AM
  • https://dl.dropboxusercontent.com/u/56669388/SetupExe%2820160115075313119C%29.log

    Ok is that it?


    Alex Olver

    Friday, January 15, 2016 12:08 AM
  • According to the logs Office itself returned 1603 which is Fatal error during installation.  Something is not correct with your install.

    Going back to the BDD.log you had success installing office on 31 Dec 2015 and 08 Jan 2016.  Did something change between then and now?


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Friday, January 15, 2016 12:21 AM
  • Hello,

    Nothing has changed... It installs on a Hyper-V machine and a laptop just seems to be a specific model but then it worked on a few of those as well?

    I manage the MDT server here and my colleague is imaging the machines... I have a log here with a successful install if you wanted to see that?


    Alex Olver

    Friday, January 15, 2016 4:25 AM
  • I can't tell if you are toying with me...

    either system temp: C:\Windows\Temp

    or the user temp: start->run->%tmp% and hit enter (it will be something like c:\users\Administrator\Appdata\Local\Temp


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.


    Yea so I knew how to get to Temp folder I just didn't know what the log file was called or if was in a sub folder.

    Alex Olver

    Friday, January 15, 2016 4:28 AM
  • browsing through your officesetuplog, it all looks fine up until Groove (onedriveforbusiness)   ...

    2016/01/15 07:55:43:553::[4512] Successfully installed package: ExcelMUI.en-us path:C:\MSOCache\All Users\{90160000-0016-0409-0000-0000000FF1CE}-C\ExcelMUI.msi
    2016/01/15 07:55:43:553::[4512] Executing chained package: GrooveMUI.en-us
    2016/01/15 07:55:43:553::[4512] Reading value of unintialized setting!
    2016/01/15 07:55:43:553::[4512] 01/15/2016 07:55:43 Installing chained package: GrooveMUI.en-us
    2016/01/15 07:55:43:553::[4512] PERF: TickCount=471203 Name=Verify MSI local install source Description=Begin function
    2016/01/15 07:55:43:632::[4512] WER element [SuppressModal] is set to value [true]
    2016/01/15 07:55:43:632::[4512] WER element [P4] is set to value [UnexpectedError]
    2016/01/15 07:55:43:632::[4512] WER element [P7] is set to value [UnexpectedError]
    2016/01/15 07:55:43:632::[4512] WER element [P6] is set to value [Unable to select Source Engine process to start]
    2016/01/15 07:55:43:632::[4512]  WER element [P6] is converted to [24A3874F]
    2016/01/15 07:55:43:632::[4512] Error: Unable to select Source Engine process to start Type: 88::UnexpectedError.
    2016/01/15 07:55:43:632::[4512] Log level changed from: Standard to: Verbose
    2016/01/15 07:55:43:632::[4512] Rolling back chain

    Your OS seems to be Win10-1509/64bit/not-LTSB:

    2016/01/15 07:53:13:005::[4512] Operating System version: 10.0.10240 . Platform ID: 2
    2016/01/15 07:53:13:005::[4512] Running 32-bit setup on a 64-bit operating system.
    This could be due to a clash with the updated NGSC for OD/ODfB or some aspect of Win10?


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Friday, January 15, 2016 6:11 AM
  • Hi Don,

    Sorry for the late response been offsite for a week or so... I am not sure what you are talking about now sorry you have lost me.


    Alex Olver

    Wednesday, January 20, 2016 5:13 AM
  • Hi Don,

    Sorry for the late response been offsite for a week or so... I am not sure what you are talking about now sorry you have lost me.


    Alex Olver

    Sorry about that :(

    You're executing the Office installation upon a Win10 machine. Win10 includes a OneDrive client, and, it may have updated itself to the Next Generation Sync Client (NGSC), which is a newer component than the OneDriveForBusiness (ODfB) which ships within Office. (The NGSC combines the OneDrive and OneDriveForBusiness client software into a single software application). The ODfB client component of Office is groove.exe.

    What I'm wondering, is if the onedrive component of Win10 could be conflicting in some way, with the onedrive component of Office, if some form of updating has occurred.


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Wednesday, January 20, 2016 10:05 AM
  • Yea so I am not sure if I have said this already but I have no issues when I run it up on a Hyper-V machine...

    So what should I do from here?


    Alex Olver

    Wednesday, January 20, 2016 9:57 PM
  • Yea so I am not sure if I have said this already but I have no issues when I run it up on a Hyper-V machine...

    So what should I do from here?


    Alex Olver


    Ah, so, the same boot method/media, same Task Sequence, same install.wim, etc, but works on VM and fails on physical?

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Wednesday, January 20, 2016 10:50 PM
  • Yea exactly that! so weird...

    Alex Olver

    Wednesday, January 20, 2016 11:03 PM
  • Can anyone help me with this? :(

    Alex Olver

    Friday, January 22, 2016 3:00 AM
  • As Don pointed out it could have something to do with Groove (OneDrive for Business) getting updated while MDT is still running.  You could also post something on the Office forums.  I think ultimately that is where your best information will come from.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Friday, January 22, 2016 10:33 AM