Reflection Workspace and Host Session Fails to Launch When Installed to a Network Drive

  • 7021496
  • 06-Jul-2007
  • 30-Oct-2020


Reflection Desktop (including Pro, for X, for IBM, or for UNIX and OpenVMS) 16.0 and higher
Reflection 2014
Reflection for IBM 2014
Reflection for UNIX and OpenVMS 2014
Reflection for IBM 2011
Reflection for UNIX and OpenVMS 2011
Reflection Standard Suite 2011


If you perform a workstation install of Reflection Desktop, Reflection 2014, or Reflection 2011 to a server share or a remote volume, Reflection may fail to launch from a network drive.


To launch Reflection, you must change the .NET Framework configuration on your workstation to grant access by following these steps:

        Reflection Desktop, Reflection 2014, and Reflection 2011 R2 or R3 require 4.0 .NET Framework.
        Reflection 2011 R1 requires 3.51 .NET Framework.
        All versions of Reflection use the core functionality provided in the 2.0 .NET Framework.
  1. Obtain the .NET Framework 2.0 Software Development Kit (SDK) from and install it to your workstation.
  2. On your workstation, go to Control Panel > Administrative Tools.
  3. Select "Microsoft .NET Framework 2.0 Configuration."
  4. Expand the tree to Runtime Security Policy > Machine > Code Groups > All_Code > LocalIntranet_Zone.
  5. In the right pane, under Tasks, click the link "Add a Child Code Group."
  6. Enter a name for the group. Click Next.
  7. Select URL from the Condition Type drop-down list, and then click Next.
  8. In the URL field, type the path to the folder where you installed Reflection. Click Next. (For example, file://Z:/Program Files/Micro Focus/Reflection/*)
  9. Select FullTrust from the "Use existing permission set" drop-down list.
  10. Click Next and Finish.


To avoid this problem, install Reflection to a local drive.


By default, .NET does not give sufficient security rights to applications that are not loaded from a local drive.

Additional Information

Legacy KB ID

This document was originally published as Attachmate Technical Note 2203.