AppV5 Office 2013 (Visio) couldn’t get published (failed configuration in folder ProgramData\App-V 0x7D401F30-0x5) RRS feed

  • Question

  • Environment:
    Server: AppV 5 SP1 Pub and Mgmt server (no Hotfixes applied)
    Client: Windows 7 SP1 x64 with AppV 5.0 SP2 client (tried RTM and with HF5)

    Created a Visio 2013 package with ODT (latest version). Only Visio, no other products added. Used the PACKAGEGUID to specify a custom PackageGUID.


    <Add SourcePath="C:\Temp\" OfficeClientEdition="32" >
    <Product ID="VisioStdVolume">
    <Language ID="en-us" />
    <Language ID="nl-nl" />
    <Language ID="fr-fr" />
    <Display Level="None" AcceptEULA="TRUE" /> 
    <Logging Name="VisioStd2013Setup.txt" Path="%temp%" />
    <Property Name="AUTOACTIVATE" Value="1" /> 
    <Property Name="PACKAGEGUID" Value="0123e69c-b152-4c70-b178-41be0d2b7d1b" />

    • Adding and Publishing locally with Powershell works like expected. But using the App-V 5.0 Mgmt/Publishing server it fails on all clients.
    • Package is published to computers.
    • Domain Computers have READ permission on the AppV Content share.
    • Previously Office 2013 packages could be published without any errors.

    AppV logs:

    Event ID: 19104:
    Part or all packages publish failed.
     published: 0
     failed: 1 
    Please check the error events of 'Configure/Publish Package' before this message for the details of the failure.
    Event ID: 1008
    Package {0123e69c-b152-4c70-b178-41be0d2b7d1b} version {5197e402-1206-4940-bd96-a0597e7d4b1f} failed configuration in folder 'C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F' with error 0x7D401F30-0x5.
    Event ID: 4001
    The App-V client failed to create a process for machine script event AddPackage with command line: '"C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=0123e69c-b152-4c70-b178-41be0d2b7d1b PackageRoot="C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=FN8TT-7WMH6-2D4X9-M337T-2342K,YC7DK-G2NP3-2QQC3-J6H88-GVGXT,C2FG9-N6J68-H8BTJ-BW3QX-RM3B3 PRIDName=VisioStdVolume'. Windows error: Access is denied..  The path must be a Windows application (.exe file).


    Analytic and Debugs logs aren’t very helpful (Client-Publishing):

    No package published.
    Published: false
    Failed: 0

    • So, Access denied (0x5) on Integrator.exe in ProgramData? As we have AppLocker in place, checked the AppLocker logs. But no trace in there.
    • Other AppV5 applications does work
    • Tested on two different App-V 5 Pub Servers (5.0 SP1 and SP1 with HF4), same behaviour.
    • Tested on three Win7 SP1 x64 clients, same behaviour.
    • EnablePackageScripts (client config) is enabled on all clients.
    • Issue was reported before on the forums, but Domain Users and Domain Computers have already READ permissions to the AppV Content Share (NTFS permissions) where the .appv file is stored.
    • Added (as a test) Domain Computers and Everyone Full Control to c:\ProgramData\App-V, doesn’t solve it.
    • Cannot use ProcMon, because the Publish event occurs before user login.

    I’m out of ideas. Someone that could assist me please?

    Monday, August 25, 2014 1:54 PM


All replies