Source: SecureLogin
Possible Cause: Terminal Launcher couldn't connect to a specified DDE emulator.
Action: Make sure that the emulator launched correctly and the emulator's DDE support is turned on.