This error comes up because it cannot find an email associated with the contact, which can be fixed via populaton/root DE OR via the contact being in all Subs. The is not related to the contact entering the journey, rather it is when it enters it errors. the high-water mark will stop it entering at all and would never generate this error.
Select a source DE with a root relationship to the contact.
Make sure the contact is above the High Water Mark on the source data.
At that point, clear the data from your data extension, re-add the rows and re-run your fire event. The reason for this need is the fire event evaluates data by the row number rather than the actual data in the DE. By clearing the data in the data extension and re-adding the data you actually create new rows of data which are then up for evaluation by the trigger. >> this clearing ensures the user is added since the last run, i.e. above the high water mark. C not compatible with JB D is the correct problem, but not correct solution. Just firing the event again will not create new rows in the data extension; https://salesforce.stackexchange.com/questions/44427/journey-builder-is-not-starting*##**##*