I recommend following these steps (run the VBScript file manually) to debug...   Open Windows Task Scheduler and locate the scheduled task that is supposed to run your project (ex. "Schedule - <projectName>"). Click the Actions tab of the scheduled task and note (copy or write down) the "Start a program" command. (For 64-bit EG, it will be something like "<fullPathToFile>\EGScript1.vbs" and for 32-bit EG something like "C:\Windows\SysWOW64\cscript.exe "<fullPathToFile>\EGScript6.vbs"".) Locate the referenced EGScript.vbs file and open it in a text editor. Scroll to the bottom of the file and remove the first single-quote at the beginning of this line to uncomment it: 'MsgBox strmsg  'Uncomment this line if you want to be notified via MessageBox of Errors in the script. Save and close the EGScript.vbs file. Open a Windows Command window (type "cmd" in the Windows Run window). Run the exact command you noted in the scheduled task. If the script fails, a message box should then appear with hopefully more useful information.  If the script runs manually with no problems, then it is likely an issue with the scheduled task.   Casey ... View more

Hi @shwms,   Double-clicking a file (ex. .sas) has the same effect as right-clicking it and selecting the Open command on the context menu.  The shell commands for .sas files are located here in the Windows registry:   HKEY_CLASSES_ROOT\SAS.Program.701\shell   The default Open command is located here:   HKEY_CLASSES_ROOT\SAS.Program.701\shell\Open\command   The default value is: "C:\Program Files\SASHome\SASEnterpriseGuide\7.1\SEGuide.exe" /openfile:"%1"   If you want a file to be opened in the same/existing EG session, the command must include the “openfile” parameter, as it is above.  If you want a file to be opened in a new EG session, the command should not include the “openfile” parameter, like so:   "C:\Program Files\SASHome\SASEnterpriseGuide\7.1\SEGuide.exe" "%1"   So, check your Windows registry and make sure that the SEGuide.exe command that is being executed when you double-click the .sas file contains the openfile parameter as in the example above.   Casey   ps- As I alluded to earlier, there can be additional .sas shell commands here in the registry:   HKEY_CLASSES_ROOT\SAS.Program.701\shell   So, if you are using the "Open with..." context menu items, rather than the default Open or double-click, it may be using those associated commands instead.  Check those commands in the registry as well and make sure they are passing the openfile parameter. ... View more

Hot fixes for this issue for SAS Studio 3.6, 3.7, and 3.71 will be available very soon.  A hot fix for SAS Studio 4.3 (on Viya) will follow not long after that.   Casey ... View more

From that error, it looks like User 2 may have EG logging turned on and that it is interfering with scheduling since they do not have permission to create a Windows Event Log appender (perhaps they don't have permission to write to the Windows Event log?).   I recommend having User 2 turn off EG logging if not already.  For example, open EG, go to Tools->Options->Application Logging, and uncheck "Enable logging" if checked.  If that does not resolve, try renaming the logging.config file in User 2's %appdata%\SAS\EnterpriseGuide\7.1 location (ex. to logging.configBAK).  Then have User 2 try to schedule again and see if it resolves.   Casey ... View more

Do you get the same error message when you attempt a test connect to your local server using the SAS Integration Technologies Configuration Wizard I mentioned in the previous thread?   Casey ... View more

Since you can't use %include (since embedded programs -- no file for server to reference), rather than referencing Program2 in Program1, you could draw an explicit link (right-click Program2 and select Link to... or hover mouse on right side of Program2 node, click and drag link line to Program1) from Program2 to Program1.  For example: Then, whenever you run the project, process flow, or branch, Program2 will always run prior to Program1.   Casey ... View more