app-v office 2013 error RRS feed

  • Question

  • Hi,

    As per the document below I was trying Create an Office 2013 package for App-V


    But at this point (setup.exe /download configuration.xml"),I am getting the following error 

    Could not install 

    Is your internet connection working ?  Do you have enough space on your main hard drive



    Sunday, May 6, 2018 3:03 PM

All replies

  • As far as I know, it is no longer supported to create native App-V Package for Office 2013 / 2016.

    See: https://social.technet.microsoft.com/Forums/en-US/367938d8-9210-4c8f-aa5e-c8de41c0a7ca/odt-2016-invalid-product-proplusvolume-specified?forum=Office2016setupdeploy

    Simon Dettling | msitproblog.com | @SimonDettling

    Please remember to mark the post(s), which answered your question.

    Monday, May 7, 2018 1:56 PM
  • Hi,

    It is supportred . 


    I can create package , it was just internet issue 

    Now new problem 

    I was trying to publish (stand alone ) , getting the below error 

    Add-AppvClientPackage -Path C:\offapp\AppVPackages\ProPlusVolume_en-us_x64.appv | Publish-AppvClientPackage
    Add-AppvClientPackage : Short file name creation (8dot3) is disabled.

    fsutil 8dot3name query  returned 2 ( enabled )


    Tuesday, May 8, 2018 6:26 AM
  • Hi did you set EnablePackageScripts?

    Roy Essers

    Tuesday, May 8, 2018 2:34 PM
  • Hi,

    I am doing this on a virtual machine . (Windows 10 enterprise ) 

    yes i Did  EnablePackageScripts

    Now here is the error i am getting 

    Log Name:      Microsoft-AppV-Client/Admin
    Source:        Microsoft-AppV-Client
    Date:          5/8/2018 6:36:21 PM
    Event ID:      14011
    Task Category: Configure Package
    Level:         Error
    Keywords:      Publishing
    User:          WINDOWS-52E3I60\test3
    Computer:      WINDOWS-52E3I60
    The package {499aec9f-a5fe-4953-98ef-4b1cd3f8d2ef} version {49b8536f-c074-46d1-897e-1ac19deaa317} could not be configured because the package is corrupt.  Ensure that the package file is a valid App-V package and try again.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
        <Provider Name="Microsoft-AppV-Client" Guid="{E4F68870-5AE8-4E5B-9CE7-CA9ED75B0245}" />
        <TimeCreated SystemTime="2018-05-08T15:36:21.711003100Z" />
        <Correlation ActivityID="{594B04A8-E6A7-0000-E18E-4C59A7E6D301}" />
        <Execution ProcessID="2076" ThreadID="3228" />
        <Security UserID="S-1-5-21-2623663482-15328344-2816252343-1002" />
        <Data Name="Package">{499AEC9F-A5FE-4953-98EF-4B1CD3F8D2EF}</Data>
        <Data Name="Version">{49B8536F-C074-46D1-897E-1AC19DEAA317}</Data>

    Here is the error on powershell console 

    Add-AppvClientPackage -Path "C:\offapp\AppVPackages\ProPlusVolume_en-us_x64.appv"
    Add-AppvClientPackage : Application Virtualization Service failed to complete requested operation.
    Operation attempted: Configure AppV Package.
    AppV Error Code: 0C80080206.
    Error module: Streaming Manager. Internal error detail: 4C402B0C80080206.
    Please consult AppV Client Event Log for more details.
    At line:1 char:1
    + Add-AppvClientPackage -Path "C:\offapp\AppVPackages\ProPlusVolume_en- ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
        + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage


    Tuesday, May 8, 2018 2:55 PM
  • it looks to me a known issue that can be workarounded by using a shorter username and then do the ODT conversion.

    let's say if your currently using is Administrator, try to create a new user called "admin", the issue should go away.

    Friday, May 11, 2018 8:26 PM
  • Hi,

    I did create admin user , then tried same error 


    Sunday, May 13, 2018 4:53 PM
  • hmm, if this is still an issue, I think you should go thru your support engineer for Office engineering team, ODT tool is supported by Office team, it is not a general AppV sequencing problem. 
    Monday, May 14, 2018 4:32 PM