none
Office 2016 / O365 - fails to create app-v package RRS feed

  • Question

  • After following https://technet.microsoft.com/en-us/library/mt590514.aspx I Get as far as running the Setup.exe /packager command where Flatter.exe fails when it tries to add files to the app-v package.

    Flatter exe error: Flattener.exe : ERROR : | 04.11.2015 09:26:59 | P:1124 | T:1 | Packaging FAILED: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)<br />Exception (outer): The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)

    The installationlog:

    11/04/2015 08:58:33.569 SETUP (0x1354) 0x1fe8 Click-To-Run General Telemetry a2xvw Medium TryLaunchClient::HandleStateAction {"MachineId": "9c5baeb449830b46baac361cfc3038b6", "SessionID": "e8d8a8b7-8209-47b7-9e50-2a6a5e749417", "GeoID": 177, "Ver": "0.0.0.0", "C2RClientVer": "16.0.6001.1034", "ContextData": "Client returned exit code: 17002"}
    11/04/2015 08:58:33.570 SETUP (0x1354) 0x1fe8 Click-To-Run Non Task Error apx75 Unexpected TryLaunchClient::HandleStateAction {"MachineId": "9c5baeb449830b46baac361cfc3038b6", "SessionID": "e8d8a8b7-8209-47b7-9e50-2a6a5e749417", "GeoID": 177, "Ver": "0.0.0.0", "C2RClientVer": "16.0.6001.1034", "ErrorCode": 17002, "ErrorType": "", "AppVErrorSource": "", "ErrorMessage": "", "ErrorDetails": "", "ContextData": "C2R client returned failing error code 17002"}
    11/04/2015 08:58:33.570 SETUP (0x1354) 0x1fe8 Click-To-Run aoh72 Medium ExitBootStateMachine::HandleStateAction: Bootstrapper workflow exiting with result: 0x0
    11/04/2015 08:58:33.570 SETUP (0x1354) 0x1fe8 Click-To-Run General Telemetry arqpm Medium AdminBootstrapper::Main {"MachineId": "9c5baeb449830b46baac361cfc3038b6", "SessionID": "e8d8a8b7-8209-47b7-9e50-2a6a5e749417", "GeoID": 177, "Ver": "0.0.0.0", "C2RClientVer": "16.0.6001.1034", "ContextData": "AdminBootstrapper::Main: Installation came back with 17002."}

    Anyone seen this before?


    Wednesday, November 4, 2015 8:58 AM

Answers

  • Wondering what is the reason but not able to find it. May be Microsoft might help when raised a ticket.

    (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    • Marked as answer by Kent Høgseth Monday, November 9, 2015 8:39 AM
    Sunday, November 8, 2015 6:00 PM
  • This week I came across the exact same issue with the latest version of ODT 2016 (v7213-5776). While running the flattener.exe it would suddenly stop as soon as it's going to add files to the package, resulting in following error in the logfile:
    Click-To-Run Non Task Error apx75 Unexpected ....."C2RClientVer": "16.1.7070.2036", "ErrorCode": 17002, "ErrorType".
    Installation came back with 17002
    The final appv package was to small (in my case 80Mb):

    Because I used ODT2016 in the past without issues, I was wandering what was going wrong. A procmon trace showed it was unable to find files, so I suppose the working directory (%temp%) was to long.
    So I started process explorer, and wrote down the argument for flattener.exe. I copied %temp%\Microsoft Office to c:\temp and renamed the folder to mso (min chars as possible). After that I ran flattner.exe again like:

    c:\temp\mso\root\flattener\flattener.exe /Source:"C:\temp\mso" /Dest:"c:\temp\mso-appv" /Version:"16.0.7070.2036" /ProductReleaseIDs:"O365ProPlusRetail" /Cultures:"en-us,x-none" /Platform:"x86" SharedComputerLicensing="0"

    And a win, the appv package was created without any errors. Of course your arguments can change depending on the version/language you're using, and the settings you chose in the config.xml. So just run procesexplorer and check. You have to run it anyways to get the Microsoft Office folder from %temp%.


    Roy Essers


    • Proposed as answer by Roy Essers Sunday, August 14, 2016 12:09 AM
    • Edited by Roy Essers Sunday, August 14, 2016 12:22 AM
    • Marked as answer by Kent Høgseth Monday, August 15, 2016 6:48 AM
    Sunday, August 14, 2016 12:09 AM

All replies

  • Are you using the latest ODT 2016 to create the package?

    Error 17002 means that write access is denied to the share. check whether the computer account has write permissions on the share. Otherwise, make sure that the computer account is a member of the domain.

    Post in your config.xml file and the exact command what you used to create. If there is any space also it might throw this error.


    (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    Wednesday, November 4, 2015 9:57 AM
  • Yes latest ODT.  Could it be that the customer doesnt not have office 2016 in their office365? I had this working on my own computer.

    c:\temp\setup.exe /download "configuration (1).xml"

    Configuration>
        <Add OfficeClientEdition="32" Branch="Business">
            <Product ID="O365BusinessRetail">
                <Language ID="nb-no"/>
            </Product>
            <Product ID="VisioProRetail">
                <Language ID="nb-no"/>
            </Product>
            <Product ID="ProjectProRetail">
                <Language ID="nb-no"/>
            </Product>
        </Add>
        <Display Level="None" AcceptEULA="TRUE"/>
        <Updates Enabled="FALSE"/>
        <Property Name="AUTOACTIVATE" Value="0"/>
        <Property Name="FORCEAPPSHUTDOWN" Value="TRUE"/>
        <Property Name="SharedComputerLicensing" Value="1"/>
    </Configuration>

    c:\temp\setup.exe /packager "configuration - Copy.xml" c:\temp\appv

    <Configuration>
    <Add SourcePath= "c:\temp" OfficeClientEdition="32" >
                <Product ID="O365BusinessRetail">
                <Language ID="nb-no"/>
            </Product>
            <Product ID="VisioProRetail">
                <Language ID="nb-no"/>
            </Product>
            <Product ID="ProjectProRetail">
                <Language ID="nb-no"/>
            </Product>
        </Add>
        <Display Level="None" AcceptEULA="TRUE"/>
        <Updates Enabled="FALSE"/>
        <Property Name="AUTOACTIVATE" Value="0"/>
        <Property Name="FORCEAPPSHUTDOWN" Value="TRUE"/>
        <Property Name="SharedComputerLicensing" Value="1"/>
    </Configuration>


    Wednesday, November 4, 2015 1:22 PM
  • Try and use the exact same xml config for both the download as the packager.
    Wednesday, November 4, 2015 10:56 PM
  • I successfully packaged office 2016/0365 using ODT 2016 last month. After seeing your post , I tried it yesterday in my lab machine. I too faced the same issue. Today I downloaded the new ODT 2016 and performed /download and then /packager. Facing the same issue again.


    (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    Thursday, November 5, 2015 5:02 AM
  • Will test and post my findings soon.

    (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    Thursday, November 5, 2015 5:02 AM
  • Excellent. I never got it working at the customer site. but at home, on my own win10 machine. Using the same config.xml it worked. So I'm stumped.

    Friday, November 6, 2015 12:34 PM
  • Wondering what is the reason but not able to find it. May be Microsoft might help when raised a ticket.

    (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    • Marked as answer by Kent Høgseth Monday, November 9, 2015 8:39 AM
    Sunday, November 8, 2015 6:00 PM
  • Probably have to. fixed it by using my own computer on a different network. I'm not going back to the environment i had problems for some time. so will not be able to test.

    Kent Høgseth

    • Marked as answer by Kent Høgseth Monday, November 9, 2015 8:38 AM
    • Unmarked as answer by Kent Høgseth Monday, November 9, 2015 8:38 AM
    Monday, November 9, 2015 8:38 AM
  • This week I came across the exact same issue with the latest version of ODT 2016 (v7213-5776). While running the flattener.exe it would suddenly stop as soon as it's going to add files to the package, resulting in following error in the logfile:
    Click-To-Run Non Task Error apx75 Unexpected ....."C2RClientVer": "16.1.7070.2036", "ErrorCode": 17002, "ErrorType".
    Installation came back with 17002
    The final appv package was to small (in my case 80Mb):

    Because I used ODT2016 in the past without issues, I was wandering what was going wrong. A procmon trace showed it was unable to find files, so I suppose the working directory (%temp%) was to long.
    So I started process explorer, and wrote down the argument for flattener.exe. I copied %temp%\Microsoft Office to c:\temp and renamed the folder to mso (min chars as possible). After that I ran flattner.exe again like:

    c:\temp\mso\root\flattener\flattener.exe /Source:"C:\temp\mso" /Dest:"c:\temp\mso-appv" /Version:"16.0.7070.2036" /ProductReleaseIDs:"O365ProPlusRetail" /Cultures:"en-us,x-none" /Platform:"x86" SharedComputerLicensing="0"

    And a win, the appv package was created without any errors. Of course your arguments can change depending on the version/language you're using, and the settings you chose in the config.xml. So just run procesexplorer and check. You have to run it anyways to get the Microsoft Office folder from %temp%.


    Roy Essers


    • Proposed as answer by Roy Essers Sunday, August 14, 2016 12:09 AM
    • Edited by Roy Essers Sunday, August 14, 2016 12:22 AM
    • Marked as answer by Kent Høgseth Monday, August 15, 2016 6:48 AM
    Sunday, August 14, 2016 12:09 AM
  • I found the actual problem to be, as eluded to by Roy Essers, that the working directory for flatterner.exe path being %temp% is too long.

    If you login with a user with a shorter name it works.  For me a two letter username worked but a 10 letter username did not.  (EG "ab" = worked vs "userxadmin" = FAILED)

    I could not believe this, I found the answer in another forum and didn't believe it but after exhausting other options tired it and walla fixed the issue.

    Oh the other problem I found is that if you have previously run the packager process it writes a key in the registry HKCU\Software\Microsoft\Office\..." and if that exists it will not even get onto flattener.  It will fail with error 170002.

    Regards

    Jason

    Thursday, August 10, 2017 5:24 AM