Attachmate.Emulation.Frame.EXE has stopped responding when loading the Reflection or InfoConnect Workspace

  • 7024003
  • 12-Jul-2019
  • 23-Oct-2020


Reflection Desktop (including Pro, for X, for IBM, or for UNIX and OpenVMS) 16.2 or higher
InfoConnect Desktop (including Pro, Unisys, and Airlines) 16.2 or higher


A message that "Attachmate.Emulation.Frame.EXE has stopped responding" can appear when loading the Reflection or InfoConnect Desktop Workspace with version 16.2 and higher.


The message indicates that the  Reflection or InfoConnect Desktop Workspace cannot find the user's My Documents folder.  Typically this means that the folder defined for the user's Documents is incorrect or that the user does not have permissions to this folder (typically this will occur with a redirected MyDocs location, and not a local PC folder location).

To determine where the Reflection or InfoConnect software is looking for the folder, run the following Windows PowerShell command:

        PS C:\Windows\system32> [Environment]::GetFolderPath([System.Environment+SpecialFolder]::MyDocuments)

The result should be something like “C:\Users\<username>\Documents”, if running from the local PC drive.  If the location returned by this Windows PowerShell call does not match where the MyDocuments is expected to be, then modify the user's Windows environment to point to the appropriate location.

Additional Information

Here is the crash information from the Windows Event Log, if Reflection or InfoConnect Desktop cannot access the user’s MyDocuments location:
    Application: Attachmate.Emulation.Frame.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.UnauthorizedAccessException
        at System.IO.__Error.WinIOError(Int32, System.String)
        at System.IO.Directory.SetCurrentDirectory(System.String)
        at Attachmate.Reflection.Core.BaseApplication.InitializeSettingsAndLogging(System.String, Boolean)
        at Attachmate.Emulation.Frame.FrameApplication.Initialize()
        at Attachmate.Emulation.Frame.Program.Main()

Feedback service temporarily unavailable. For content questions or problems, please contact Support.