About CaseySmith

CaseySmith · ‎04-26-2018

If you are using a Yoga (touchscreen device) with Windows 10, then it is certainly possible you are running into the Microsoft issue (specific to Windows 10) that crashes EG. To reproduce this crash, click to the left of a line in EG's code editor (ex. a simple libname statement) to select the line. Notice that the selection includes an extra space at the end which represents the line-ending and that the caret is positioned inside the selection, rather than at the end (this appears to be a contributing factor)... Now submit this code (press Run or F3), switch back to the Program tab, and then EG should crash... To confirm you are encountering this issue, look in the Windows Event Viewer (in Windows Logs->Application) after the crash and if you see an Error whose faulting module is tiptsf.dll, then you are encountering this issue. We worked with Microsoft to identify this bug in their code. Microsoft promised a fix soon in a Windows 10 update, which we are awaiting. UPDATE: The fix has now been provided by Microsoft, in their Windows 10 April 2018 Update. You can workaround the issue by avoiding clicking to the left of the lines to make your selection. For example, start your selection by clicking in the text area rather than to the left of the text area, or use the keyboard to make your selection. This avoids the caret being inside the selection (which appears to contribute to the problem), thus avoids the crash. If you are encountering a different issue... Are there any details associated with the "crash" that you can share? For example, is there a dialog with a callstack perhaps? Vheck the Windows Event Viewer to see if there are other Errors in the Windows Logs->Application log that provide more information. You can also turn on EG logging from within EG via Tools->Options->Application Logging (then close EG, restart EG, reproduce the crash with as few steps as possible, then save off the EG log). I suggest contacting SAS Tech Support. They will likely ask for the information above. If you share some of it here, I might be able to provide more guidance. Casey

CaseySmith · ‎04-26-2018

What exact version of EG do you have (in Help->About dialog)? If your externally referenced .sas files have not changed, yet you are still getting prompted whether to save them, then that is a bug. I suggest upgrading to the latest version and update (7.15 HF3) if you are able, which may resolve the issue. Otherwise, I suggest opening a track with SAS Tech Support. Casey

CaseySmith · ‎04-03-2018

We do have plans to add a background submission feature to EG in a future release, very similar to the one in SAS Studio. We do not know exactly when it will make it in though. Casey

CaseySmith · ‎03-23-2018

There is support for this starting in EG 7.15. See this post for details: https://communities.sas.com/t5/SAS-Enterprise-Guide/Auto-Purge-Project-Log-in-EG/m-p/436983/highlight/true#M28212 Casey

CaseySmith · ‎03-21-2018

Yes, you can print custom warnings (or errors or notes) to the SAS log via put statements in SAS code. For example, if you submit this somewhere in your SAS code... %put WARNING: You are doing something I need to warn you about!; ...it will show up in the log and the log summary view, like so: (Use "%put ERROR: error text;" or "%put NOTE: note text;" for custom errors or notes.) Granted, you'd have to be able to detect the scenario you wish to warn via code, so your code knows when to conditionally print the warning. That might be difficult with the example you mentioned. Casey

CaseySmith · ‎03-21-2018

It's hard for me to visualize the issue you are describing. I can say though that the order the process flow runs independent (unlinked) items is from top-to-bottom, left-to-right. For example, if you have two independent program nodes side-by-side in the process flow and the one on the right is just slightly higher than the one on the left, the one on the right will run before the one on the left. (Linked items should always run downstream.) I'm not sure it will make a difference with this specific problem you are seeing, but I did notice that you are running the originally shipped EG 7.13 (with no updates applied). Several updates have been released that have addressed a number of issues. You can download the latest EG 7.13 update from here: http://ftp.sas.com/techsup/download/hotfix/HF2/A3V.html Casey

CaseySmith · ‎03-21-2018

That (your Citrix configuration) is almost certainly the issue then. Your EG options are stored in this xml file (in your appdata user location): %appdata%\SAS\EnterpriseGuide\7.1\EGOptions.xml (ex. C:\Users\<userid>\AppData\Roaming\SAS\EnterpriseGuide\7.1\EGOptions.xml) It sounds like your Citrix environment is not preserving updates to that file between sessions, thus changes to your EG options are lost. Casey

CaseySmith · ‎03-01-2018

If you haven't already seen, checkout Chris' blog post on autoexec options in EG: https://blogs.sas.com/content/sgf/2014/05/01/autoexecs-the-sas-enterprise-guide-advantage/

CaseySmith · ‎02-27-2018

Thanks @Proc_Fail. That (avoiding posting logs publicly) makes sense. I see the track and have access to the EG log you provided. We are investigating and will communicate back through Tech Support. Casey

CaseySmith · ‎02-27-2018

Happy to help. Yeah, the previous was just an example of using a PowerShell script to drive the EG automation interface. You can customize it to do whatever operations you are interested in. For example, here is a PowerShell script that clears the project log for the specified EG project and shows examples (commented out) of other project log operations you could perform: $project = 'C:\temp\deleteme\Project1.egp' $eguideApp = New-Object -ComObject SASEGObjectModel.Application.7.1 $egProject = $eguideApp.Open("$project","") $projectLog = $egProject.ProjectLog Write-Host "Clearing the project log in EG project: " $project # Clear the project log: $projectLog.Clear() # Other available project log operation examples... # Enable/disable project log: #$projectLog.Enabled = $true # Get project log text: #$strProjectLog = $projectLog.Text #Write-Host "Project log text: " $strProjectLog # Save project log to a file: #$projectLog.SaveAs("c:\temp\deleteme\projectLog.txt") # Email project log: #$toList = @("me@here.com") #$ccList = @() #$projectLog.SendMail("", "", $toList, $ccList, "my subject", "my body text") $egProject.Save() $egProject.Close() $eguideApp.Quit() Write-Host "Done." Casey

CaseySmith · ‎02-23-2018

Here is an example of using the EG automation interface from PowerShell: $projectList = @('C:\temp\deleteme\Project1.egp','C:\temp\deleteme\Project2.egp') foreach($project in $projectList) { Write-Host "Start processing of " $project $eguideApp = New-Object -ComObject SASEGObjectModel.Application.7.1 $egProject = $eguideApp.Open("$project","") $egProject.run() $egProject.save() $egProject.close() $eguideApp.Quit() Write-Host "Ended processing of " $project } Same objects and methods are available (since registered COM interfaces), just PowerShell syntax. The script above opens, runs, saves, then closes two EG projects, one after the other. Casey

CaseySmith · ‎02-23-2018

We'd like to take a look at your EG log to see if we can identify where the slowdown is occurring. You can turn on logging in EG via EG's Tools->Options->Application Logging. Check "Enable logging", note the log folder location (open Windows Explorer to it), then close EG. Then reproduce the problem in a new EG session and after the "freeze" (when the UI becomes responsive again), copy the generated log file to a different location (to limit the logging to only the problem scenario). It's probably best to open a SAS Tech Support track for this issue, describing the problem, steps to reproduce, and attach the EG log. The track should come to us here in R&D. If you want to also attach the EG log to this thread, we can take an early look. Casey

CaseySmith · ‎02-23-2018

In the EG Query Builder (screenshot below), drag the variables you want to group by (ex. CASE_ID, Activity_Creator, Decisioned_By, and Agency_Date (but not Suspect_Reason, since different values) into selected columns (on the Select Data tab). Then, in the Summary column, select MAX. Notice the summary groups will be automatically selected (at the bottom). Now run the query and you should get the results you desire. If you want the full records, you could then left join that query result back with the original table. Casey

CaseySmith · ‎02-23-2018

Have you compared the performance of clicking the Commit button in EG to another Git GUI (ex. Git Extensions, SourceTree, etc.) to see if it is specific to EG or not? Casey

CaseySmith · ‎02-23-2018

It won't help you right now, but we are planning on adding a "Run branch to here" feature in a future release, which sounds like it might help your scenario. It will be similar to the existing "Run branch from here" feature, except rather than running all the downstream nodes, it will run all the upstream nodes and then stop at the node from which you ran the command (rather than continuing execution down the branch). Casey

Online Status	Offline
Date Last Visited	‎10-09-2025 07:58 AM