This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Found this thread in my inbox. As it turns out, there was a restriction on the Alteryx server that blocked it from running WScript.exe
IT had never tried this before and the person who runs security was never looped into the discussion. About 6 weeks later, we happened to bring it up when she was around and she said "Oh, yeah, of course this wouldn't work."
I've found this thread really helpful in trying to set up my workflow that calls a VBA macro. I've found the best set up has been to use wscript.exe to run a VB script (which has slightly different syntax from VBA) that then opens an Excel file that contains the VBA macro and runs it. Unfortunately, now I really do find myself stuck with this error message coming up. I know this is more a Windows/VB question, but has anyone seen this before and able to help?
This is frustrating because the script does manage to open the .xlsm file before getting to this error message. And when I manually go into Excel and run the macro, it runs! (So it's not disabled or unavailable.)