Hi Lachlan,

One possible work-around would be to start by creating your new CONN project using the GUI (no need to enter any info there, just create a blank conn project with the same name as the conn project that the batch script is then going to use) before actually running your batch script. That should allow the batch script to work just fine while using the stand-alone version without running into this issue.