Default appv Office 2013 package fail

I created office 2013 package with ODT.
Before tweaking the package I decided just to see if default configuration will work. So I didn't exclude any product from the package and want to see the result of Office language. I found the info that Office will take the OS language by default
and I distribute it to test Windows 7 French.
For a test I copied the AppVPackages folder created by ODT containging .appv to Content share and Published the package to computer group containing 2 test computers.
I get this error in eventvwr on client machine:
Package {d24c3bdd-8fad-44d3-998c-933f8f053682} version {047f1eb5-96e8-416b-9231-31f7030afd6c} failed configuration in folder 'C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\047F1EB5-96E8-416B-9231-31F7030AFD6C' with error 0x79100710-0xD.
Do I have to change something in ProPlus_x86_DeploymaneConfig.xml prior publishing?
I renamed AppvPackages folder containing .appv and xml files more distinguished name on Content share. Could it be the reason of error?
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

No, you should not require to change anything in the Deployment Configuration XML file.
Can you get a sequenced Office 2013 to work in any scenario e.g. on an English language machine for example?
PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
rorymon.com Twitter: @Rorymon

Similar Messages

Office 2013 Packager failed: Office (32-bit) not packaging because of Office (64-bit)

Hello,
I used ODT to download Office 2013 Pro 32-bit and now I am trying to create a package from those files. I use the command line:
Setup.exe /packager configuration.xml "E:\Office 2013 Pro App-v"
When I try to run this, I immidiatly get the following message:
"We found a problem! We're sorry, Office (32-bit) couldn't be installed because you have these 64-bit Office programs installed on your computer. Microsoft Office 2013. 32-bit and 64-bit versions of Office programs don't get along, so you can only have
one type installed at a time. Please try installing the 64-bit version of Office instead, or uninstall your other 64-bit Office programs and try this installation again."
I checked my installed programs on the server, but I don't have Office 2013 64-bit installed. I did in the past create packages for Office 2013 64-bit , but it's currently not in published/installed on the server. I checked with revo uninstaller to be sure.
Is there a registry setting, or something that is misleading App-V to believe I still have Office 2013 64-bit somewhere installed? I really need to stream MS Access 32-bit to users. But cannot solve this issue.
Thanks in advance,

Hello,
Thanks for replying. Your solution works, BUT I'm immidiatly running into a second problem. The .appv package that is created, cannot be published. The error I get is:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
I think this has to do with issues in the september releases of Office 2013. I'm gonna try downloading a previous versin using ODT. Changing the configuration.xml file to:
<Configuration>
<Add SourcePath="E:\DGI Applicaties\DGI Office 2013 Pro" OfficeClientEdition="32"
Version="15.0.4631.1002" >
    <Product ID="ProPlusVolume">
      <Language ID="nl-nl" />
<ExcludeApp ID="Excel" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Infopath" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
<ExcludeApp ID="Powerpoint" />
<ExcludeApp ID="Project" />
<ExcludeApp ID="Publisher" />
<ExcludeApp ID="SharePointDesigner" />
<ExcludeApp ID="Visio" />
<ExcludeApp ID="Word" />
    </Product>
</Add>
    <Updates Enabled="False" />
    <Display Level="None" AcceptEULA="TRUE" />
<Logging Name="Office2013_package.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

Office 2013 updates fail on computers with Access 2013 installed

I have about 10 workstations with the combination of Windows 7 enterprise 32 bit, Access 2013 and Office 2007 installed.
SCCM offers up both Office 2007 and Office 2013 updates to these machines, but the Office 2013 updates, fail to install.
The same thing happens when I go to Microsoft updates and manually install the required Office 2013 updates.
I read that one of the updates required Office 2013 sp1.
But when I downloaded it, it won't install: KB2817430 "The expected version of this product was not found on the system."
This is the second month I've had the failures. I removed KB2878316 and KB2889927 from my deployments and packages to stop repeated install attempts.
But this month I've got a new on failing, KB2899493.
Is there a way around this problem?

Thanks, I couldn't really find anything but it looks as though this could be just the way it is.
from http://support.microsoft.com/kb/2784668
When you start a version of Access on a computer that has multiple versions of Access installed, the Windows Installer may start, and
a message that states that the Windows Installer is preparing to install Access may be displayed before Access starts.
Every time that you start Access 2003, Access 2007, or Access 2010 after you use Access 2013, the Windows Installer repair operation registers
that version of Access. Similarly, the Windows Installer repair operation registers Access 2010 every time that you start it after you use an earlier version of Access. This does not occur when you start Access 2002, nor does it occur when you start the same
version of Access again.
Is this likely to also apply even when running App-V?

Sccm 2007 office 2013 package downlown issue

Dear Exprt,
we have receive common issue with office 2013 package download.
[email protected]

Please check that all the files have been copied to the distibution point check the logs for errors and check the distibution package from the server share. Also make sure that the SCCM has correct rights the get the source material AND that the path to
source material is set correctly and contains no errors. When running the advertisement at the client side could you check that the local cache contains all the files you have set into the distribution point.

Office 2013 SP1 fails with code 17302 - SCCM 2007 R2

Hi,
I am trying to deploy Office 2013, along with SP1, in the following order:
1. Prompt to close all office apps and continue (vbs)
2. Installation of Office 2013, using modified msp.
3. Restart
4. Installation of SP1 with command line /passive /norestart.
I am doing this all through a package I created in SCCM 2007 R2.
The first few programs works well. However, when the installation of SP1 starts, SCCM launches the program, then SP1 fails with code 17302.
Manual installation, through command prompt, with the same switches works fine.
The error is only when remotely deploying.
The system is Windows 7 X86 with latest SP.
Please help!

Hi,
Have you checked the log file? Does it say anything there? Also, where is the SP1 installation file stored? Since this only happens while remotely deploying, check the network or the setting of your filewall.
By the way, you can slipstream Service Pack 1 with your Office 2013 installation media, Office 2013 will be directly installed at Service Pack 1 level, saving you the trouble of applying it afterwards. For the details, please refer to this article:
http://www.howto-outlook.com/otherprograms/slipstreamoffice2013sp.htm
(Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Microsoft Office can't find your license for this application - multiple copies of Office 2013 x32 failing to start, Software Protection Service timing out

We're experiencing a growing problem with our users in several different domains running in to Microsoft Office 2013 x32 'activation' issues. We use KMS for licensing, which works properly, but some of the machines (~20-30 out of 1000+) sporadically
throw the following error:
'Microsoft Office can't find your license for this application. Microsoft Office will now exit.'
We know it's not an issue with the licenses per se, since they work on and off and we can force KMS activation correctly / talk to the KMS servers.
It appears to be an issue with the Software Protection service not starting properly. In Event Viewer, we see the following:
'Software protection service failed to start due to the following error- the service did not respond in a timely fashion.
Event 7000'
This is occurring on a variety of machines in a variety of environments, all fully patched with the latest Office updates. It's inconsistent, and the 'manually restart the Software Protection Service' solution is not viable as it's occurring on many
different workstations. Office repairs have also been unsuccessful.
Has anyone else come across this? Or have any idea why the Software Protection Service might be sporadically failing? Maybe an Office update in the last 2-3 months?
Thanks for any info.

We're experiencing a growing problem with our users in several different domains running in to Microsoft Office 2013 x32 'activation' issues. We use KMS for licensing, which works properly, but some of the machines (~20-30 out of 1000+) sporadically
throw the following error:
'Microsoft Office can't find your license for this application. Microsoft Office will now exit.'
We know it's not an issue with the licenses per se, since they work on and off and we can force KMS activation correctly / talk to the KMS servers.
It appears to be an issue with the Software Protection service not starting properly. In Event Viewer, we see the following:
'Software protection service failed to start due to the following error- the service did not respond in a timely fashion.
Event 7000'
This is occurring on a variety of machines in a variety of environments, all fully patched with the latest Office updates. It's inconsistent, and the 'manually restart the Software Protection Service' solution is not viable as it's occurring on many
different workstations. Office repairs have also been unsuccessful.
Has anyone else come across this? Or have any idea why the Software Protection Service might be sporadically failing? Maybe an Office update in the last 2-3 months?
Thanks for any info.

Uninstall App-v office 2013 package sccm 2012

Hi ,
how do we add uninstall command to office 2013 appv appliation in sccm 2012, i see no option were we can give command lines unlike normal msi apps.
please confirm
Thanks

Please take a look at this previous thread:
https://social.technet.microsoft.com/Forums/en-US/6663cb6e-23c1-48e6-a62e-85c447b88f3d/appv-application-uninstall-with-sccm-2012-integration?forum=mdopappv
PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
rorymon.com Twitter: @Rorymon

Office 2013 Installer - Fails with No Errors

Hello,
I ran into issues on two different Windows 8 (64-bit) machines today, both with Office 2013 Pro Plus (32-bit) installed. I could not get the installer to come up to add a module (or make any other changes).
On one of the PCs, I tried running the Fixit to remove Office, since the option of the "Online Repair" was not accessible, (installer would not start). Fixit removed Office, but after a reboot, it still would not run the office installer, even
with Office 2013 completely gone.
Things I tried:
- Disabled anti-virus (windows defender)
- Run with elevated privileges (I'm a domain admin and UAC is off, but just to be safe)
- Removed skydrive
- Cleaned out temp directory
- Scanned for registry errors (none)
- Re-downloaded the installer DVD
- Made sure no pending windows update
- Reboots (lots of times, definitely after the uninstall)
- Checked the install log in %temp%, this is what I get:
2013/08/12 13:51:14:263::[2848] PERF: TickCount=1295931 Name=OBootStrapper::Run Description=Begin function
2013/08/12 13:51:14:264::[2848] Operating System version: 6.2.9200 . Platform ID: 2
2013/08/12 13:51:14:264::[2848] Running 32-bit setup on a 64-bit operating system.
2013/08/12 13:51:14:264::[2848] Command line: "F:\SETUP.EXE"
2013/08/12 13:51:14:264::[2848] No command line arguments given
2013/08/12 13:51:14:513::[2848] Verify file signature in "F:\SETUP.EXE"
2013/08/12 13:51:14:562::[2848] F:\SETUP.EXE is trusted.
2013/08/12 13:51:14:562::[2848] Verify file signature in "F:\proplus.ww\OSETUP.DLL"
2013/08/12 13:51:14:598::[2848] F:\proplus.ww\OSETUP.DLL is trusted.
2013/08/12 13:51:14:612::[2848] Using setup controller dll at [F:\proplus.ww\OSETUP.DLL].
2013/08/12 13:51:14:612::[2848] PERF: TickCount=1296274 Name=OBootStrapper::Run Description=Calling RunSetup
This is almost identical to what I see on the other PC, except with different drive letters.
THERE ARE NO ERROR MESSAGES - no popup, no installer dialog - nothing, which makes it really hard to troubleshoot. And it's happening on both Windows 8 machines that have had Office 2013 installed. I am so frustrated right now after wasting half of today
troubleshooting this.
Any thoughts?

Hi
Let’s follow these steps:
Make sure you have end the tasks of setup.exe and integratedoffice.exe.
   1. Press the Ctrl + Alt+ Delete key -> Click on Task Manager to open.
   2. Under Processes tab -> Select setup.exe -> Click on End Process.
    3. Under Processes tab -> Select integratedoffice.exe -> Click on End Process.
  Restart the computer in Clean Boot and install Office 2013. Follow the steps:
       http://support.microsoft.com/kb/929135
   Note: After you have finished troubleshooting in clean boot, ensure you restart the computer in normal mode.
In addition, you can also refer to the following link to try more methods:
http://support.microsoft.com/kb/2822317/en-us
Regards

Microsoft NuGet - Visual Studio 2013 package failed

I had to do a system restore on my machine and then re-install of Visual Studio and I have now twice gotten this error message. So can anyone tell me what's up with this message I can't make heads or tails from the log file it's huge which stands to reason
since the install must have taken nearly 30 minutes.
I did find this from a google search which didn't offer much reason for optimism...
http://stackoverflow.com/questions/27671562/microsoft-nuget-package-installation-failed-error-while-installing-visual-st

Hi net2rd,
Thank you for posting in MSDN forum.
Based on your issue, you mean that when you are also trying to install the VS2013 Community with Update 4 and the get the error message, am I right?
If yes, to check this issue is related to the VS setup file or the OS environment. I suggest you could try to install the same version of VS on other machine check if you get same error message.
(1) If you get same error message on other machine, I doubt that this issue may be related to your VS setup file. SO I suggest you could try to re-download the VS2013 Community from the Microsoft Official and then install it check this issue.
Reference:
http://www.visualstudio.com/en-us/news/vs2013-community-vs.aspx
If you still could not install it successfully, since I am not the VS install experts. So I suggest you can post this issue to the VS Install forum:https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=vssetup
, you will get better support.
(2) If you did not get same error on other machine, I doubt that the issue may be related to your OS environment. I suggest you could try to repair or re-install the OS check this issue.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

The configuration file did not contain well formed AppV configuration XML - When using Office 2013 ODT package

All,
I'm experiencing an issue where when using the Office 2013 package pulled down from ODT, that if I try to change the locations of either InfoPath Filler 2013 or Publisher 2013 from the default of Microsoft Office 2013 then I receive the message "The
configuration file did not contain well formed AppV configuration XML. Please check the management server event log for more information". If I check Applications and Services\Microsoft\AppV\Server-Management\Admin the error displayed there is "An
error was encountered parsing dynamic configuration file '0'. However I am able to change the shortcut location for all other applications except the above 2. I've tried redownloading the files using the ODT and also changing the version number (so far I've
tried both the 15.0.4631.1002 and 15.0.4659.1001 with the same result).
As all I'm interested in so far is having a package which contains Visio and Project I've tried following the article to exclude all the other Office elements:
http://technet.microsoft.com/library/jj219426(v=office.15).aspx#BKMK_ExcludeAppElement. However the package looks to be the same and when I load it into the management console all the options and elements to Office 2013 are available like they were before
when I hadn't set the exclude tags so I'm not sure whether the ExcludeApp parameters actually work correctly.
This then brings me onto the 3rd issue I've experienced. I have a group for the Visio users and I've set custom security for them to have Visio delivered to them but not Project and then a seperate group for just Project users who will have Project delivered
to them but not have Visio. When testing this sometimes seems to work but other times it seems to trip out and a user just in the Project or Visio group will get all of the Office 2013 applications and under the default location of Microsoft Office 2013. When
trying to spot correlation with this it appears random and can happen to any user on any device. We have sequenced a few applications ourselves where different parts are needed for different users and we have successfully managed this using different security
groups for different applications, just as I'm trying here with Office 2013.
Has anyone else experienced the issue with the "did not contain well formed XML" as at the start of the post and how were you able to resolve this? Also has anyone any advice on how to troubleshoot the issue with the security seeming to trip out
and publish all applications within a package to a user regardless of whether they are in the correct group or not?
The management / publishing servers are 5.0.1224.0 which is SP1 HF4 and the clients are on SP2 HF5.
Thanks

Nicke,
The config files are UTF-8. I did find the same article as yourself, however when searching for the value ‘TakeoverExtensionPointsFrom46=’ within either of the configuration.xml files that text isn’t found.
No sinister reason not to share the file used, just it’s the same structure as referenced in the article:
http://technet.microsoft.com/en-us/library/dn745895(v=office.15).aspx. The only difference being that I’m using ProPlusVolume and I’ve set a version number (which is the October
2014 update). I’ve even looked to follow the above example as closely as possible in just using the ExcludeApp ID of Access and InfoPath, just to try and prove the process. However I still get the usual full package. The version of the Click-to-Run setup.exe
I’m using is 15.0.4623.1001, so later than the version specified at the end of that article which is 15.0.4619.1000. Where can I expect to see the elements excluded? Will it be when loading the package into the management console or would it just not appear
on the machine when delivered?
<Configuration>
<Add SourcePath="C:\OfficeDeploymentToolV2" Version="15.0.4659.1001" OfficeClientEdition="32">
    <Product ID="ProPlusVolume">
      <Language ID="en-us" />
<ExcludeApp ID="Access" />
<ExcludeApp ID="InfoPath" />
    </Product>
</Add>
</Configuration>
3). We’ve not used global publishing in our environment yet so I will try that. I’ve set both GlobalRefreshEnabled and GlobalRefreshOnLogon to True and when using the command Get-AppvPublishingServer on the client I’m testing with I can see this is pulled
through correctly. I’ve also added the client name to the AD group used to grant access to the package and it is published. However nothing is pulling through onto the Client, so are there any steps I’ve missed or misinterpreted when looking to set this up?
I guess the global publishing is there to keep in with licensing for Office being per device? On a slight aside, as Windows licensing is being changed to allow per user licensing
http://www.zdnet.com/microsoft-to-make-per-user-windows-licensing-available-to-enterprise-customers-7000035401/ does anyone know if there are any plans to allow for Office / Project / Visio licenses to go per user as well? We’re a volume license customer
rather than subscription based so I think a lot of the options to selectively deploy Visio and Project are excluded for us.
Dan,
Ok that explains why the security could be tripping out then and leading to this result. As above I’ll try with global publishing and see how I get on.
From what I’ve read / watched I think only one Office 2013 package can be published to a machine, so we would be unable to have a separate package for Visio and a separate package for Project and then attempt to deliver
them both together. If a user wanted both Project and Visio then I guess we’d need to have a combined Project and Visio package to cover than scenario, but then 2 more separate Project and Visio packages for those who would only want either Project and Visio
(I think).
The scenario we’re looking at is to see whether we are able to deliver Project and / or Visio to different users through an AppV package and this will then cover users on XenApp or on fat clients. Only a small proportion of our
users will need access to Project and / or Visio so therefore we’d only have a small amount of Project and Visio licenses.
However from what I’ve tested up to this point and from what I’ve picked up from Forum posts / watched on TechEd sessions is that as publishing is Global and is unable to use different security groups for different elements of the
suite, then using Office through AppV is only suitable if you will be delivering the whole suite (including Project and Visio) to all of your users. So in a scenario where you’d only want certain elements to be delivered to a handful of users then you’d need
to keep with traditional ESD methods to have this installed onto fat clients and steer clear of XenApp. If wanting to install to XenApp then a lockdown tool like AppSense or AppLocker would also need to be brought into the equation.
Is my understanding above correct or have I missed some options / methods?
If the full Office package is always delivered but a company only has Office licenses and no Project and Visio licenses for all its users, how do they stop Project and Visio being delivered and being available? Or again if you have
this use case is the AppV method one which will be unsuitable?
Thanks

Office 2013 VL and app-v 5 SP2 on RDS server - package add fails with script error

We have used the MS Office Depolyment Tool for click-to-run to download the latest Office 365 version, and flatten it into an app-v 5 package - not a problem.
When we try to add the package to our client machine (Server 2008R2 running the app-v 5 SP2 client software), it fails with an message that a script has failed and not returned a 0 code. We have not added any scripting to this automatically created
package, so it seems that the app-v client does not like the "official" package. Any hints and tips gratefully accepted, thanks
App-v client has scripting enabled.
The powershell command line we are using is:
PS C:\windows\system32> Set-ExecutionPolicy Unrestricted
PS C:\windows\system32> Add-AppvClientPackage -path file://hostname/app-v/o365-noaccess/ProPlusVolume_en-us_zh-cn_x86.appv -DynamicDeploymentConfiguration \
\hostname\app-v\O365-NoAccess\ProPlusVolume_en-us_zh-cn_x86_DeploymentConfig.xml
with a result of:
Add-AppvClientPackage : Embedded Script process exited with an error code indicating failure (return code other than 0). Please ensure that Embedded
Script process can complete successfully and exits with 0.
Operation attempted: Configure AppV Package.
AppV Error Code: 100000000C.
Please consult AppV Client Event Log for more details.
At line:1 char:1
+ Add-AppvClientPackage -path
file://hostname/app-v/o365-noaccess/ProPlusVolum ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
    + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage
and these are the error messages we see in the debug app-v client logs:
Script Launcher successfully waited for script with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=D24C3BDD-8FAD-44d3-998C-933F8F053682
PackageRoot="C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
PRIDName=ProPlusVolume'.
and...
Package {d24c3bdd-8fad-44d3-998c-933f8f053682} version {cd9725ce-4503-4932-863b-4fcda3f9551d} failed configuration in folder 'C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D' with error 0x79100E10-0xC.
and...
machine script for event AddPackage with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe"'
exited with failure error code: The extended attributes are inconsistent.. Because Rollback is set to true in the script definition, the current AppV Client operation was rolled back.
We believe this last error message is the kicker, but can't debug any further.

Just to validate the problem, I started again.
I have just downloaded the latest ODT from MS, and then downloaded the latest Office 2013 packaged - volume license. Then created the app-v package - all went perfectly, no error messages. Uploaded the package to the app-v 5 server and published
it. I have made NO changes to any of the files.
I have just built a brand new Windows Server 2008R2 Datacentre VM, patched it to the hilt, and installed the RDS role, powershell 3 and appv 5.0 SP2 client for RDS.
I then use powershell as above:
          scripting unrestricted
          app v client scripting enabled
         app v server added
          global and user update enabled
         add-appvclient package "url of office package.appv"
             and received exactly the same error message.
It is not complaining that scripting is not allowed, it is complaining that the script is invalid.
Help!!!!

Office 2013 appv package upgrade to new service pack

scenario:
Office 2013 SP1 is published.
SP2 become available. What would be the steps for SP installation?
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Create a new package using the same steps as the first, the Office deployment tool will download and package the latest version available by default (by which time hopefully Microsoft have fixed the issue where the latest version doesn't convert to App-V
successfully!).
Then deploy the package as an update as you would for any other package. Since the package GUID should be the same for all Office 2013 packages unless you manually changed it, the App-V client should treat this as an upgraded package and only stream down
the blocks that have been updated.
Dan Gough - UK App-V MVP
Blog: packageology.com
Twitter: @packageologist
LinkedIn

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

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.
Configuration.xml;
<Configuration>
<Add SourcePath="C:\Temp\" OfficeClientEdition="32" >
<Product ID="VisioStdVolume">
<Language ID="en-us" />
<Language ID="nl-nl" />
<Language ID="fr-fr" />
</Product>
</Add>
<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" />
</Configuration>
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?

The above fix was a lucky shot.
This solved it (hopefully) for good;
http://www.the-d-spot.org/wordpress/2014/11/05/appv5-office-2013-package-cannot-be-published-access-is-denied-on-integrator-exe/

Office 2013 PACKAGEGUID

Hi everyone,
I am having trouble generating an Office 2013 package with a different package GUID. Here is my XML
<Configuration>
<Add SourcePath="C:\officeproplus\" OfficeClientEdition="32" >
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="1" />
<Property Name="PACKAGEGUID" Value="12345678-ABCD-1234-ABCD-1234567890AB" />
</Configuration>
I basically copy pasted the XML from here;
http://www.applepie.se/office-2013-and-unique-appv-pkg-id
I see a lot of forum posts talking about the ability to choose the package GUID, but nothing that would point to what I'm doing wrong.
The package created has the same default package GUID (here is a snippet from the deployment XML)
<?xml version="1.0" encoding="utf-8"?>
<DeploymentConfiguration PackageId="D24C3BDD-8FAD-44d3-998C-933F8F053682" DisplayName="Microsoft Office 15 ProPlusVolume_en-us_x86" IgnorableNamespaces="" xmlns="http://schemas.microsoft.com/appv/2010/deploymentconfiguration"
I did try publishing just in case and the package GUID is definitely the D24 one, not the one I am choosing in the XML.
When I look at flattener.log, it shows me the packageGUID being set as the default;
Flattener.exe /PackageGUID:D24C3BDD-8FAD-44d3-998C-933F8F053682
In the packagerparameters.txt file I also see similar.
What am I doing wrong?

Hello,
You must use the latest version;
http://www.microsoft.com/en-us/download/details.aspx?id=36778
Nicke Källén | The Knack| Twitter:
@Znackattack

Publishing office 2013 on app-v server

Hi,
I'm trying to publish an office 2013 package that I have created using the ODT.
The technet guide (http://technet.microsoft.com/en-gb/library/dn817830.aspx) I am using is telling me to use this command 'Add-AppvClientPackage <Path_to_AppV_Package> | Publish-AppvClientPackage
–global'  from the client and then 'From
the Web Management Console on the App-V Server, you can add permissions to a group of computers instead of to a user group to enable packages to be published globally to the computers in the corresponding group.' from
what I can see it has worked as in I can now open word, excel etc.. but the package has not appeared on the appv server yet to allow me to configure permissions. Before attempting the above command I tried importing the package directly into the app-v
web management console but the app-v client could not see the package although it was in the correct security group.
Any pointers?
Thanks

+ note that it may take several minutes (10+) before a new published package appears on the client
Falko
Twitter
@kirk_tn   |   Blog
kirxblog   |   Web
kirx.org   |   Fireside
appvbook.com

Default appv Office 2013 package fail

Similar Messages

Maybe you are looking for