No, it isn't destination related. The excel source just shuts the ssis operation down ie. won't bring over anything if I activate that particular column in the mapping of Excel Source transform.

If I enable the mapping for this column in the Excel source and subsequently on the OLE DB destination, then it fails at the source. If I disable the mapping on each end then all the other columns flow.

Nothing happens downstream of the Excel Source the moment I activate that one column.

That is why within excel I have been trying various column formats: custom, general, text. Here's a sample of what one may find in that column within Excel:

Backflow - Plumbing, 2.5"inch > Penthouse Mechanical Room