A long shot, but does it fail if you try this command instead (without fully-qualified path to .egp file, since it appears to be in the same folder as your .vbs)?
C:\Users\Dreamy\Desktop\ExtractCode>cscript ExtractCode_v7.vbs Qtr_ZZZZ.egp
Or if you put the files somewhere other than your Desktop?
Reason I ask is that I can reproduce the same error when the .egp file cannot be located. Your script works fine for me (using 32-bit 7.15 HF8; I didn't try 64-bit, but I'd expect it to work for me too). (The Qtr_ZZZZ.egp file I created simply contains a single program with the code "proc print; data=sashelp.class; run;".) However, I initially saw the same error when I ran this command (note, I'm using 32-bit EG, thus the 32-bit cscript.exe):
c:\Windows\SysWOW64\cscript.exe "C:\Users\cassmi\OneDrive - SAS\Desktop\ExtractCode_v7.vbs" "C:\Users\cassmi\Desktop\ExtractCode\Qtr_ZZZZ.egp"
The reason I got the error is because "C:\Users\cassmi\Desktop\ExtractCode\Qtr_ZZZZ.egp" doesn't physically exist on my machine. I can paste "C:\Users\cassmi\Desktop\ExtractCode" into Windows Explorer and it routes to my Desktop fine, but then if I look at the path in the address bar, I see it mapped to "C:\Users\cassmi\OneDrive - SAS\Desktop\ExtractCode". Windows Explorer knows to map "C:\Users\cassmi\Desktop" to my physically mapped Desktop location, but the command window doesn't (since "C:\Users\cassmi\Desktop" is also a physical location, but not the one my Desktop is mapped to).
I'm guessing you are running into a different issue, since your command prompt shows "C:\Users\Dreamy\Desktop\ExtractCode" physically exists (so your Desktop is probably not mapped), but worth confirming that the path to the .egp file you are passing in physically exists in the context of the command window (ex. dir "C:\Users\Dreamy\Desktop\ExtractCode\Qtr_ZZZZ.egp").
If you confirm it exists, then I'd try a trivial project, such as the one I described earlier (containing a single, simple program).
If still no luck, I second Chris' recommendation of turning on EG logging and then inspecting the resultant cscript_log.*.txt logs in the EG log location (ex. %appdata%\SAS\EnterpriseGuide\7.1\Logs) and search it for errors or exceptions.
Casey
... View more