Attachmate.Emulation.Frame disappears from memory using WS-Discovery printer for Print screen in UTS session

  • 7022866
  • 18-Apr-2018
  • 23-Oct-2020

Environment

InfoConnect Desktop for Unisys 16.1
Microsoft Windows 10

Situation

The Attachmate.Emulation.Frame.EXE will crash or just disappear from memory (taking the open host session with it) when using a WS-Discovery (WSD) network connected printer as the Default Windows printer on Windows 10.  This problem only occurs when selecting Print screen commands in a UTS session, whereas 3270 and T27 sessions seem to work fine.  The problem occurs when selecting File | Print… or File | Print Settings… and a message will appear that the “Attachmate.Emulation.Frame.EXE has stopped working”, or the InfoConnect host session and InfoConnect Workspace will just close with no error.

If the WS-Discovery printer is NOT the Default Windows Printer or if the check box in the Print Settings dialog that says “Use Windows Default printer” is unselected than the problem does not occur.  If the network connected printer (WS-Discovery) is instead set up to be connected to Windows 10 with a Standard TCP/IP port or via USB Port it will work fine.  The problem only happens with WSD printers.

Resolution

This is currently being evaluated by Micro Focus Development and may be resolved in a future release.

Workaround Steps:
Do not set the WSD printer as the Default Windows Printer or else set up the WSD printer as a Standard TCP Port or USB Shared printer to the Windows 10 workstation.

Status

Reported to Engineering

Additional Information

Fault details:

Faulting application name: Attachmate.Emulation.Frame.exe, version: 16.1.348.0, time stamp: 0x5a2baab4
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6
Exception code: 0xc0000409
Fault offset: 0x000a46a9
Faulting process id: 0x1734
Faulting application start time: 0x01d3c5ef30c5fdae
Faulting application path: C:\Program Files (x86)\Micro
Focus\InfoConnect\Attachmate.Emulation.Frame.exe
Faulting module path: C:\Windows\SYSTEM32\MSVCR120.dll
Report Id: 0a30c627-f875-40b2-86ce-42ba193696b1

Fault bucket 1579903702803818090, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: Attachmate.Emulation.Frame.exe
P2: 16.1.348.0
P3: 5a2baab4
P4: MSVCR120.dll
P5: 12.0.21005.1
P6: 524f7ce6
P7: 000a46a9
P8: c0000409
P9: 00000005

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