thank you for your comment...
What is different is that we are bringing in a csv file so we need to choose the 'open database' option which is where the issue resides. We do a lot of bat file automation where the import is a report (not database/csv/etc...) and they all run fine. In this instance, we created a project that opens a csv (database option) and performs the exports successfully only when we run the project manually (not thru a bat command). We need to run this through a bat file.
How are you calling the csv file, model and export in the .bat file? I have a bat file with something like this.
Monarch.exe /datasource:"[path]\Sample.csv" /mod:"[path]\ModelName.xmod" /exptable:"ExportTableName" /exp:"[path]\ExportName.xlsx"
If my datasource is an excel file or an access file, I just add /table:"TableName" after datasource.