Product Documentation

Troubleshoot App-V

Nov 04, 2014

Troubleshoot Studio

Test connection operation fails

If the Test connection operation returns an error when you specify App-V management server and publishing server addresses in Studio, check the following:
  1. The App-V server is powered on: either send a Ping command or check the IIS Manager (each App-V server should be in a Started and Running state).
  2. PowerShell remoting is enabled on the App-V server. If it is not, follow the procedure in http://technet.microsoft.com/en-us/magazine/ff700227.aspx.
  3. The App-V server is added to Active Directory.

    If the Studio machine and the App-V server are in different Active Directory domains that do not have a trust relationship, from the PowerShell console on the Studio machine, run winrm s winrm/Config/client ‘@{TrustedHosts=”<App-V server FQDN>”}’. If TrustedHosts is managed by GPO, the following error message will display: “The config setting TrustedHosts cannot be changed because use is controlled by policies. The policy would need to be set to “Not Configured” in order to change the config setting”. If this message displays, add an entry for the App-V server name to the TrustedHosts policy in GPO (Administrative Templates > Windows Components > Windows Remote Management (WinRM) > WinRM Client).

  4. The Studio administrator is also an App-V server administrator.
  5. File sharing is enabled on the App-V server: enter \\<App-V server FQDN> in Windows Explorer or with the Run command.
  6. The App-V server has the same file sharing permissions as the App-V administrator: on the App-V server, add an entry for\\<App-V Server FQDN> in Stored User Names and Passwords, specifying the credentials of the user who has administrator privileges on the App-V server. For guidance, see http://support.microsoft.com/kb/306541.

App-V application discovery fails

Check the following if App-V application discovery fails:

  1. Studio administrator is an App-V management server administrator.
  2. The App-V management server is running. Check this by opening the IIS Manager and make sure the server is in a Started and Running state.
  3. PowerShell remoting is enabled on the App-V management server and on the publishing server. If either is not enabled, follow the procedure in http://technet.microsoft.com/en-us/magazine/ff700227.aspx to enable the server.
  4. Packages have appropriate security permissions so that the Studio administrator has access.

Troubleshoot App-V launch failure

Check the following if App-V applications fail to launch:

  1. The publishing server is running. Check this by opening the IIS Manager and make sure the server is in a Started and Running state.
  2. App-V packages have appropriate security permissions so that users have access.
  3. Check the following on the VDA:
    • Make sure that Temp is pointing to the correct location, and that there is enough space available in the Temp directory.
    • Make sure that App-V client is installed, and no earlier than version 5.0.
    • Make sure you have Administrator permissions, run Get-AppvClientConfiguration and make sure that EnablePackageScripts is set to 1. If it is not set to 1, run Set-AppvClientConfiguration -EnablePackageScripts $true.

      Citrix recommends that you perform this step when you create a master image so that all VDAs created from the master image have the correct configuration.

    • Access the Registry editor (regedit) and go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\AppV. Make sure that the AppVServers key has the following value format: AppVManagementServer+metadata;PublishingServer. For example:
      http://xmas-demo-appv.blrstrm.com+0+0+0+1+1+1+0+1; 
      http://xmas-demo-appv.blrstrm.com:8082
    • Make sure that CtxAppVCOMAdmin has administrator privileges. During VDA installation CtxAppVCOMAdmin is usually created and added to the Local Administrators Group on the VDA machine. However, depending on the Active Directory policy, this user might lose the administrative association.

      Run compmgmt.msc and browse to Local Users and Groups > Users. If CtxAppVCOMAdmin is not an administrator, fine tune the group policy or contact your administrator, so that this user account retains its administrative association.

  4. On the master image on which the App-V client is installed, the administrator must set the PowerShell ExecutionPolicy to RemoteSigned. This setting is required because the App-V client module provided by Microsoft is not signed, and this the setting allows PowerShell to run unsigned local scripts and cmdlets. Set the ExecutionPolicy using one of these methods:
    • Logged in as administrator, run the PowerShell command Set-ExecutionPolicy RemoteSigned.
    • From Group Policy settings, go to Computer Configuration > Policies > Administrative Templates Windows Components > Windows PowerShell > Turn on Script Execution.
  5. Check the publishing servers:
    • Run Get-AppvPublishingServer * to display the list of publishing servers.
    • Check whether UserRefreshonLogon is set to False. If it is not set to False, the first App-V application launch typically fails.
    • With Administrator privileges, run Set-AppvPublishingServer and set UserRefreshonLogon to False.
    Note: Beginning with XenDesktop release 7.1 or XenApp 7.5, you can view and set UserRefreshOnLogon (and other publishing servers parameters) using SDK cmdlets.

If these steps do not resolve the issues, the Administrator should enable and examine the logs.

After upgrading an App-V package

If you upgrade an App-V package containing applications published through Studio, delete the old applications, which will remove them from the application Delivery Group. Then, discover and add the new applications to the Delivery Group. For example, if you published Word 2010 and Excel 2010 from an Office 2010 App-V package and then upgraded that package to Office 2013, remove Word 2010 and Excel 2010 and then discover and add Word 2013 and Excel 2013.

Enable logs

Enable logs on Studio and the VDA to help troubleshoot App-V.

To enable Studio logs

  1. Create the folder C:\CtxAppvLogs.
  2. Go to C:\ProgramFiles\Citrix\ StudioAppVIntegration\SnapIn\Citrix.Appv.Admin.V1, and open CtxAppvCommon.dll.config in a text editor such as notepad as an administrator. Uncomment the following line:
    <add key =”LogFileName” value=”C:\CtxAppvLogs\log.txt”/> 
    

    The logs are available at that location.

To enable VDA logs

  1. Create the folder C:\CtxAppvLogs.
  2. Go to C:\ProgramFiles\Citrix\ Virtual Desktop Agent, and open CtxAppvCommon.dll.config in a text editor such as notepad as an administrator.
  3. Uncomment the following line in CtxAppvCommon.dll.config:
    <add key =”LogFileName” value=”C:\CtxAppvLogs\log.txt”/> 
    
  4. Uncomment the following line and set the value field to 1 as shown in the following example:
    <add key =”EnableLauncherLogs” value=”1”/>
    • All configuration related logs are available in C:\CtxAppvLogs.
    • The application launch logs are available as follows:
      • XenDesktop 7.1, XenDesktop 7.5, or XenApp 7.5 — %LOCALAPPDATA%\Citrix\CtxAppvLogs.
      • XenDesktop 7.0 — %LocalAppData%\temp\CtxAppVLogs
    • LOCALAPPDATA resolves to the local folder for the logged in user. Make sure to check in the local folder of the launching user (for whom application launch failed):
      • Beginning with XenDesktop 7.1 or XenApp 7.5 — %LocalAppData%\Citrix\CtxAppVLogs\.
      • XenDesktop 7.0 — %LocalAppData%\temp\CtxAppVLogs\
  5. As Administrator, restart the Broker service or restart the VDA machine to start logging.