Further to an earlier post i did relating to a similar error message I did come across this issue again in 2 separate environments. Oddly v.uneven in how often it would happen but it would only occur with the app-v published applications we had.
Summary of environments
Both Xenapp 7.13
VDA’s running 7.15
Published to VDA’s running MCS and PVS images respectively.
Band-aid fix was to reset the profile in Director. Did see instances of “bad” profiles having files in their AppData\local\Microsoft\Credentials folder but a removal didn’t do anything.
Ultimately came down to controller version. Upgrading environments to the 7.15 LTSR resolved the issue. If you review the readme for 7.15 it details the fix specifically:
When launching an App-v package using the Microsoft App-V 5.0 infrastructure integrated with XenDesktop, the App-V package might fail to synchronize and the following exception occurs:
“Cannot start <applicationname>” [#LC5483]
Shout out to Wendell who posted some great recommendations regarding the above setup – will definitely save some time for folks in the long run particularly relating to UPM configuration piece and getting that right, details enclosed:
Recently came across this question on the citrix discussions and must say Martin has come up with a novel approach to what could of required a more complicated solution – see thread below:
From time to time might encounter issues relating to your WMI provider service. This service interacts directly with the SCCM client so is an important one as would affect in a lot of cases to patch your systems. Have seen this pop-up moreso in pre-2012 r2 environments but still does.
Regards automating fixes for this issue there is an auto-recover facility that comes with Window server OSes 2008 r2 or later.
on how to enable.
Recently setup a pool of Citrix VDA’s (7.16) to house app-v packages for publication using SMB/Single Admin mode.
On setting up (thought I) followed all the steps outlined in:
but missed a key action on first pass, when launching my app in citrix i would get the “cannot Start <App-name>” message (pretty common and not terribly informational 🙂
Anyways said the key action i did miss was as per above eDoc:
“Tip: After you install the App-V client, with Administrator permissions, run the PowerShell Get-AppvClientConfiguration cmdlet, and ensure that EnablePackageScripts is set to 1. If it is not set to 1, run Set-AppvClientConfiguration -EnablePackageScripts $true.“
Once implemented was all good to go.
Recently been getting to grips with WEM as part of a proof of concept and run it through its paces as a possible tool to use as part of a Windows 10 project. Pretty good tool so far must say, installation straightforward enough, interface intuitive – looks like it was built by folks who would use it themselves which is always a good sign.
Does take a little bit of looking around to find some of the settings you might be looking for, for me I want to dump the folder redirection settings had in place in our GPO into it. To enable from within the WEM administration console need to click on (as per below pic):
i) On left hand pane Policies and Profiles
ii) Click Microsoft USV Settings
iii) Tick the box beside Process User State Virtualization Configuration
From there the options within the 2 Folder Redirection tabs (1/1 and 2/2) will be available so you can start using them for the usual contenders eg desktop/my documents etc
Last week got the error enclosed in article sure as eggs in our 6.5 environment. Effect came a week after we had moved to hotfix rollup pack 7 – had done UAT for half a week but wasn’t detected.