About CaseySmith

megalopsuchos · ‎08-29-2019

Thank you Casey. I would also like to mention, I opened an incident with SAS support as well and here something the technician added about the EG:Tools:Connections:Modify Profile:Authentication Domain field: The 'Authentication domain:' field should not contain your active directory domain, this field is used to specify the SAS authentication domain that should be used to start the workspace server. Remove the entry and you should no longer see the prompt for the workspace server. Also, the shared settings path for me is here: AppData\Roaming\SAS\SharedSettings\7.1

CaseySmith · ‎08-27-2019

To see an example of VBScript that can be used to execute an EG project (rather than SAS code directly as in your example), schedule a project in the EG interface, which will create an EGScript.vbs file you can inspect. Casey

CaseySmith · ‎08-15-2019

This is a known issue that was fixed in EG 7.12 HF2 and 7.13, so I'm assume you are using an earlier version? If you are using EG 7.12, installing the latest 7.12 HF should resolve the problem. If you are using a version prior to 7.12, upgrading to 7.13 or later (I recommend the latest... 8.1) should resolve the problem. Casey

CaseySmith · ‎08-15-2019

I'm glad switching the results format (ex. to SAS Report) is a reasonable workaround for now. Note: The HTML results format in EG 7.15 used the ODS HTML/HTML4 destination. EG 8.1 uses ODS HTML5 by default. I suspect the issue is specific to ODS HTML5. So, another workaround (if you prefer to stick with html) may be to use HTML4 instead of HTML5 in EG 8.1 (select "Use HTML" radio button, instead of "Use HTML5", in EG's Tools->Options->Results->HTML). In other words, I have a feeling using any results format other than HTML5 would avoid the issue. Casey

boureg · ‎08-11-2019

Many thanks for your answer. However, the option outencoding does not work with libname + pcfiles statement. Since, the NORSASIOTRANSERROR option is valid for the whole SAS environment, I cannot use this option.

SASKiwi · ‎08-09-2019

Running your processes in batch mode via a scheduler would give you a greater level of control. You can arrange so that if a "project" fails then following steps don't run. You can also use the SAS option SYNTAXCHECK to immediately stop processing any more data once an error occurs. In batch mode you get a full log all processes and it is very easy to locate errors (with simple text searches) and then to fix them. Of course the down side is you would have to export your projects to SAS code to run in batch mode.

CaseySmith · ‎08-08-2019

Yes, please open a track with SAS Tech Support. We'd like to get more details about the problem you are seeing, in hopes that we can reproduce, diagnose, and fix. Casey

CaseySmith · ‎08-06-2019

Yes, this has been improved in EG 8.1. When the Show full details when viewing SAS Libraries in File Dialog details view option (in EG's Tools->Options->General) is checked (off by default), if you right-click a table in the Servers pane and select Properties you will see the row count, along with other detailed info. For example: Additionally, when that option is on, EG's file open dialog will show the row counts along with other info in the Details view. For example: (This feature (the extra details in the FOD) has existed for many EG releases, but the extra details in the data set properties dialog from the Servers pane is new to EG 8.1.) Note: The option is off by default only because it can take slightly longer to query for the additional detailed info. Of course, alternatively, you can always submit SAS code to retrieve the record count (query the sashelp.vtable dictionary table as @Technolero showed or run proc contents on the desired data). Casey

CaseySmith · ‎08-06-2019

I was curious, so gave it a shot, but as you'll see from this log snippet, it only returns the filename: 76 filename myfile FILESRVC folderpath="/Users/cassmi" filename="yo.txt"; 77 %put %sysfunc(pathname(myfile)); yo.txt Also, there isn't really a way this (getting a path that references a file from SAS Content, but can be used in a server file system context) could work, since there is no full path to this file (in server file system context). The file doesn't exist on the server file system. It only exists in the SAS Content location. Casey

CaseySmith · ‎08-06-2019

Hi Isek, Yes, execution (via scripting) is by process flow, project, or individual items. There isn't an easy way to run just a single branch in a process flow via the scripting interface. I'm glad organizing by process flow allows you to accomplish your goal. Casey

ChrisHemedinger · ‎08-06-2019

Hi @PhilC - no, I don't expect that Java would have any impact on this. EG does not rely on Java in the process.

CaseySmith · ‎08-05-2019

The SAS Studio 3.7 hotfix (C7W003) with the fix for this issue has been released, but it appears it hasn't been applied to the SAS OnDemand for Academics servers yet. I inquired to see if I can find out the plans for when it will be applied. UPDATE: I just got word that the hot fix is planned to be applied next week, so it should be resolved soon. Casey

AltadenaCheetah · ‎07-18-2019

I think it is a corrupt SAS EG project that is causing the problems. Not sure how to fix it other than to start a new project and set it up the same way. Kind of a pain, but not too bad, I guess.

CaseySmith · ‎07-18-2019

That looks to be an installation issue related to the Microsoft Visual C++ runtime redistributable and possibly the .NET Framework (components that EG relies on). Yeah, I'd contact SAS Tech Support. Casey

CaseySmith · ‎07-16-2019

EG 7.15 HF8 surfaced this problem... EG 7.15 (prior to HF8) was incorrectly storing editor settings in this 8.1 registry location (as you noted): HKEY_CURRENT_USER\Software\SAS Institute Inc.\Enhanced Editor\BIC_8.1 (should have been BIC_7.1) 7.15 HF8 updated EG 7.15 to use this corrected location instead: HKEY_CURRENT_USER\Software\SAS Institute Inc.\Enhanced Editor\BIC_7.1 However, that means any editor customizations that you made prior to that are still in the BIC_8.1 registry location instead of the BIC_7.1 registry location (where 7.15 HF8 is now looking). The easiest way to get your customizations back is to "copy" the registry settings from BIC_8.1 to BIC_7.1 via the export/import instructions Tech Support provided to @EStrom1. Casey

Online Status	Offline
Date Last Visited	a week ago