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

  • 7022866
  • 18-Apr-2018
  • 02-May-2018


Infoconnect Desktop for Unisys 16.1
Microsoft Windows 10


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.

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
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


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.

Additional Information

Steps to Duplicate:

1. Create a Windows 10 machine with all the latest Microsoft security and other updates.

2. Install Infoconnect Desktop for Unisys 16.1

3. Create and save a UTS session.

4. Setup a Windows printer that supports WS-Discovery (WSD - Web Services Dynamic Discovery) on the network.
    Most network capable printers built in the last 5-10 years support the WS-Discovery protocol.

5. Install the Windows 10 printer driver.
        a) Go to the printer manufacturer website and get the latest printer drivers for Windows 10
        b) Install the printer driver on Windows 10 and when prompted, do not choose USB
           but make sure to select network connected printer.
        c) Let the printer driver installation software find the network printer
        d) The printer drivers will be installed locally on Windows 10
        e) Uncheck the setting “Let Windows manage my default printer”
        f) A reboot of Windows 10 might be necessary

6. Set up Windows 10 with the default printer set for a printer that supports WS-Discovery (WSD - Web Services Dynamic Discovery)
        a) In Windows 10 open up Settings / Devices / Printers & Scanners
        b) Select "Add a printer or scanner"
        c) Windows 10 will search for a printer or scanner
           If a printer is not found select "The printer I want isn't listed" and then
           select “Add a Bluetooth, wireless, or network discoverable printer”
        d) Uncheck the setting “Let Windows manage my default printer”
           Set this printer as the Default Windows printer
        e) Verify you can access and print to this printer from Windows applications like Notepad

7. Open the Infoconnect Workspace and UTS session defined in step 3 above

8. Go to the File menu

9. Select Print…
    Select Print Settings…

10. An error will appear that the Attachmate.Emulation.Frame.EXE has stopped working or
      else the Infoconnect Host session and Infoconnect Workspace will just close with no error.