About Nigel_Pain

Nigel_Pain · ‎03-15-2023

I think you are maybe under a misapprehension here. To use SAS Studio, you need a functioning copy of base SAS somewhere, whether that is on your own workstation or a server. It will therefore give you access to all the functionality that you get from a Base SAS installation. In the latter case, you would require an installation including the SAS mid-tier server products. SAS OnDemand for Academics is a free, online service. As far as I'm aware, there are fairly tight restrictions on data sizes. Not quite sure what these are though.

Nigel_Pain · ‎03-02-2023

OK, I think I've got to the bottom of it, and it looks like it's the Office Add-In rather than SAS itself. There's an AMO setting "SAS results files location" which looks like it's set by default to a user's home drive. Where AMO was installed before the move to OneDrive that would be the UNC to their H: drive. So any time they opened Word, Excel or Powerpoint it tried to recreate that if it didn't exist.

Nigel_Pain · ‎03-01-2023

Thanks @gwootton . I reckoned maybe ?FOLDERID_Documents did something like that. But I have replaced it with %appdata% in the sasv9.cfg file so it shouldn't be an issue anymore. We're still seeing the folders being recreated in a few cases. Actually I have a suspicion that it's nothing to do with SAS itself, but a hang-over in their Windows account profiles. One of them doesn't ever use SAS (might have done in the past though).

Nigel_Pain · ‎02-28-2023

SAS 9.4M7 on Windows Server 2012R2 and EG 8.3 on Windows 10 Up until recently, all users in our organisation had an H: home drive mapped onto Windows shared drives. We have now replaced these with OneDrive as part of our MS365 rollout. Unfortunately, when the infrastructure folk were removing the H: drive folders they found that some were being recreated with a "My SAS Files" subfolder. I suspected that this was due to SAS assigning SASUSER to this location. The sasv9.cfg had the following lines: -SET MYSASFILES "?FOLDERID_Documents\My SAS Files\9.4" -SASUSER "?FOLDERID_Documents\My SAS Files\9.4" I don't quite understand what sort of reference "?FOLDERID_Documents" is but I guessed it was possibly pointing users to the UNC path of their old home drives. So I changed these lines to refer to locations in the users' profiles: -SET MYSASFILES "%APPDATA%\My SAS Files\9.4" -SASUSER "%APPDATA%\My SAS Files\9.4" However, we are still seeing some of the old home drive locations being recreated. Does anyone have any ideas how this is happening? There are no other references to anything which could be the old home drives in the sasv9.cfg file or the various autoexec files used by Workspace Servers. Thanks.

Nigel_Pain · ‎02-09-2023

If you check the properties of your calculated item you'll probably find that the Aggregation is set to "Sum", so that it's effectively multiplying the number of days in the year by the number of records. in the table. Change it to "Average", "Minimum" or "Maximum" and it should display the correct value.

Nigel_Pain · ‎02-06-2023

Aye, it is to do with AMO. I've had a few support calls come in within my organisation where it wasn't working, turned out AMO was not installed or not enabled. They got this message: Starting Excel made no difference. Installing/enabling the Add-In fixed it.

Nigel_Pain · ‎02-06-2023

To be fair, if you have EG and AMO, you can right-click the output in EG and send it to Excel: But the Excel download from Studio does work well from what I've seen.

Nigel_Pain · ‎02-06-2023

Thanks for this, I've never seen that method before. Works very well.

Nigel_Pain · ‎01-09-2023

I see what you did there, @SASKiwi!

Nigel_Pain · ‎11-08-2022

I'm sorry @SASJR1, hadn't noticed the OLAP or PC Files Server services. I don't know about them because they aren't in our environment. At a guess, they won't be dependent on any others (especially PCFF) so chances are you could just put them in anywhere. After Metadata anyway, and possibly after the Object and Connect Spawners? @AndyForeman might be able to give you an answer? He's been working on a brilliant wee Powershell script for starting and stopping services in the correct order. https://communities.sas.com/t5/Administration-and-Deployment/SAS-wsm-is-available-for-use-with-SAS-9-4-deployments

Nigel_Pain · ‎11-07-2022

If you're just stopping everything, the order doesn't really matter a huge amount. The order for restarting is more important. Here's the order we use (we have all of those, plus a few others): SAS [Config-Lev1] SASMeta - Metadata Server SAS [Config-Lev1] Web Infrastructure Platform Data Server SAS [Config-Lev1] Object Spawner SAS Connect Spawner SAS[config-Lev1]DIPJobRunner SAS [Config-Lev1] JMS Broker on port 61616 SAS [Config-Lev1] Cache Locator on port 41415 SAS[Config-Lev1]httpd-WebServer SAS [Config-Lev1] SASServer1_1 - WebAppServer SAS [Config-Lev1] SAS Environment Manager SAS [Config-Lev1] SAS Environment Manager Agent SAS Deployment Agent If you really want to adhere to a stopping order, just reverse this. Interested that you don't have a SASServer2_1 Web Application Server? Our system uses that for SAS Studio and Environment Manager.

Nigel_Pain · ‎11-04-2022

Here you are @AndyForeman (or anyone else who wants it). Feel free to do what you like with it. No guarantees on how well it works, it seems to work for me but I don't have a good testing environment to try it properly. I understand very much about not publicising your email address.

Nigel_Pain · ‎11-03-2022

I've managed to modify the script to handle services over multiple servers. The config file is comma separated with service and server names and there's an extra array definition containing the server names as well. @AndyForeman if you want it I can send it to you to do what you wish with it. I haven't got to grips with Git I'm afraid.

Nigel_Pain · ‎10-28-2022

There's a couple of things here. First, if a user can see the library in EG then they must have ReadMetadata permissions to it. Consider only granting RM to users who need to see it. Second, in EG 8.3 there is a setting to hide unassigned libraries from the list so by default any libraries which aren't pre-assigned will not be visible. You can toggle it from a button at the top of the Servers pane: Compare these: To be clear, the second library in the second picture is greyed out because it's not assigned. It is hidden in the first picture. The circled button toggles this setting.

Nigel_Pain · ‎10-28-2022

This is great! Thanks Andy (and also Greg Wootton who I think might have first conceived of the idea). I'm having a bit of a think to see if it can be modified to cover services running on multiple servers, that would be quite cool.

Online Status	Offline
Date Last Visited	‎12-08-2025 05:07 AM

Re: Suggestions for Managing SAS Enterprise Guide Updates

Re: Suggestions for Managing SAS Enterprise Guide Updates

Re: Running the SMU

Re: Running the SMU

Re: Running the SMU

Running the SMU

Re: SASHFADD blocked by group policy

Re: Considerations for Updating to SAS 9.4 M8

Re: Considerations for Updating to SAS 9.4 M8

Re: Users removed from accessing the library

Re: clinical sas

Re: AMO integrated into SAS Studio

SAS-wsm is available for use with SAS 9.4 deployments

Re: Automate rebuilding and redeploying web apps

Re: connection to OneDrive

Re: Suggestions for Managing SAS Enterprise Guide Updates

Re: Suggestions for Managing SAS Enterprise Guide Updates

Re: Mid-Tier config drive keeps filling up

Re: ODBC Connection from SAS 9.4 M6 on Windows Server Cannot see tabl...

Re: Metadata Migration Preserve Permissiosn

Re: SAS studio vs base SAS

Re: Windows users home drives

Re: Windows users home drives

Windows users home drives

Re: Return Days of Year from Now()

Re: AMO integrated into SAS Studio

Re: AMO integrated into SAS Studio

Re: AMO integrated into SAS Studio

Re: SAS 9.4 Base and STAT for Windows under Parallels on a Mac with an...

Re: SAS stopping order services

Re: SAS stopping order services

Re: SAS-wsm is available for use with SAS 9.4 deployments

Re: SAS-wsm is available for use with SAS 9.4 deployments

Re: How to hide libraries in EG even I do not have access

Re: SAS-wsm is available for use with SAS 9.4 deployments

SUGA