I encountered the same issue. It turned out my script was using the Sybase version of BCP instead of Microsoft's, due to Sybase appearing earlier in the system's PATH variable. To resolve this, you can either adjust the PATH order to prioritize Microsoft tools or explicitly specify the full path to bcp.exe from the Microsoft SQL Server utilities.