I resolved this by adding the SQLSERVER user with full permissions to the folder that contained the csv file. As mentioned in other environments this was not needed to work. Hopefully this helps someone else suffering form the same annoyance!
I resolved this by adding the SQLSERVER user with full permissions to the folder that contained the csv file. As mentioned in other environments this was not needed to work. Hopefully this helps someone else suffering form the same annoyance!