I encountered this one today, it was because something had uninstalled the SSM agent, but since the existing processes were still running, I could still attempt to connect.