As it turns out, the problem was not with ExecuteGlobal
, but instead with the .vbs file I was attempting to import. The file I was importing was not in ANSI encoding. If VBScript has a problem with the file you are importing, it will report the error at the character and line for the beginning of ExecuteGlobal
(which admittedly causes confusion).
Open the file you are attempting to import, convert it to ANSI and everything should work.