Source: SecureLogin
Possible Cause: Terminal Launcher couldn't find a session file for an emulator.
Action: Configure Terminal Launcher to have the correct path to the file for the emulator session.