Hi,
We've got an issue where large App-V packages fail to install from the app catalog, however if you install them manually, running exactly the same command that SCCM uses the package is added without issue. e.g.:
ErrorMessage=Insufficient memory to continue the execution of the program.FullyQualifiedError ID =System.OutOfMemoryException,Microsoft.AppV.AppvClientPowerShell.AddAppvPackageContext:Severity=WarningHostName=ConsoleHostHostVersion=3.0Host ID =96138c86-1713-4774-b231-027a57e28ad3EngineVersion=3.0Runspace ID =82791baf-5bd0-412b-af81-e4c3a3b63ae3Pipeline ID =1CommandName=Add-AppvClientPackageCommandType=CmdletScriptName=CommandPath=SequenceNumber=15User= xxx\SYSTEMShell ID =Microsoft.PowerShellUserData:
This is the command used by SCCM (from appenforce.log):
Executing Command line: "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" -ExecutionPolicy Bypass import-module 'C:\Program Files\Microsoft Application Virtualization\Client\AppvClient\AppvClient.psd1'; Add-AppvClientPackage -Path 'C:\Windows\ccmcache\o\MathLab MatLab r2012b_2_3.appv' -DynamicDeploymentConfiguration 'C:\Windows\ccmcache\o\MathLab MatLab r2012b_2_3_DeploymentConfig.xml' with system context
If I open a PS command window as myself and run exactly the same command, copy and pasted from that log, there is no issue. The app appears and is usable.
What could be the difference between SCCM executing this with the SYSTEM account causing it to run out of memory?
Thanks