This happens if the SQL Server agent isn't running. This situation should be logged at WARN level, as otherwise the connector silently is running but no events are produced in streaming mode.