Ah... thanks, Baub -- remember in the future to post error messages... that would have made this quick and easy to answer for you:
The MS Office "engine" used, to export to Excel, only accepts Unicode text (NVARCHAR in SQL, or DT_WSTR in SSIS). It will not accept ASCII text (VARCHAR in SQL, or DT_STR in SSIS).
The easiest approach, I find, is to convert the column in T-SQL. Since you said length=50:
Column2Export = CONVERT(NVARCHAR(50), OriginalColumn)
An alternative approach is to do it in SSIS, though I think that's a lot more work. In your your Data Flow Task, you would add a Data Conversion component, in between the Source Component and Destination Component. Why that's more work: click on data types for each column... and needing to do it again if the layout ever changes. If you do the conversion in T-SQL, then SSIS can auto-detect the new column by you just recreating the source, the arrow, and the destination. The Data Conversion component is not all auto-detect.
For more information, see both answers on sister site dba.StackExchange.com:
https://dba.stackexchange.com/questions/41608/converting-non-unicode-string-to-unicode-string-ssis
(The 2nd answer there talks about the downloadable component "replacing data conversion"... but I see that as still more work than a T-SQL conversion.)