Column EonRunErrors does not belong to table
Marc, did you ever find a solution to this? I am encountering the same thing and would really like to know if you have a solution.
In our case, we had to turn on
/* Style Definitions */
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
font-family:"Times New Roman",serif;}
the “Log Errors” and “Log XML” options for the map in SmartConnect and look at the XML to see what the errors were.
Not sure what happened with the formatting on my previous answer. I’ll try again…
We had this issue too. Turns out there was an error in the data, but our version of SmartConnect had a bug where the error wouldn’t get reported on the Process Errors window, and selecting “Highlight Errors” would just give the “Column EONERUNERRORS” message.
In our case, we had to turn on the “Log Errors” and “Log XML” options for the map in SmartConnect and look at the XML to see what the errors were.
If you would like to submit an answer or comment, please sign in to the eOne portal.