XenApp 6.x – Resolving Published Windows Explorer Closing Straight Away

XenApp 6.x – Resolving Published Windows Explorer Closing Straight Away

Introduction

This article provides the steps required to resolve an issue where a Published Windows Explorer application closes straight away on XenApp 6.x when launched first by a user.

This artlice is split in to the following sections :-

  • Symptoms
  • Cause
  • Identifying The Issue
  • Resolving The Issue

Symptoms

When a user launches a Published Windows Explorer application first, the application appears to load, the Citrix Progress dialog box completes but the Published Application does not open.

This issue only appears to occur if the user launches the Published Windows Explorer application first, if it is launched after other Published Applications it works without issue.

Cause

The issue is due to the ICA Client sometimes needing more time to establish the connection to the XenApp Server and timing out.

Identifying The Issue

To identify whether this is the issue perform the following steps :-

  • Check the Application Event Logs on the XenApp Server or Servers for the following error being logged when the user attempts to launch the application

Event ID – 9009

Source – Desktop Window Manager

Details – The Desktop Window Manager has exited with code (0x40010004)

If this error is logged when the user attempts to launch the Published Windows Explorer application first then perform the steps in the next section

Resolving The Issue

To resolve the issue you will need to add a ten second delay so tha the ICA Client has time to establish the connection. To add a ten second delay perform the following steps :-

  • Open regedt32 on the XenApp Server
  • Navigate to the Registry Key below :-

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\Wfshell\TWI

  • Add the new registry setting below :-

Name – LogoffCheckerStartupDelayInSeconds

Type – REG_DWORD

Value – 10 (Decimal)

  • The registry fix above does not require a reboot to become active

If you need to apply the fix to multiple servers in a farm then the easiest way is to deploy it using a Group Policy Registry Preference Policy.