SAS 9.4M7 on Windows Server 2012 R2. Four servers (Metadata, compute, mid-tier, LASR) I had a few issues with Environment Manager this morning so restarted the server and agents. Since then it has been showing an availability issue for the SAS Application Server Tier. I suppose I don't really know what this one is. The documentation suggests that it is something to do with the metadata server. Does anyone have an idea how I troubleshoot this further? All other monitored resources seem to be OK.  Thanks ... View more

SAS 9.4M7 on Windows 2012R2 I just renewed the SSL certificate on our mid-tier server, and the Java keystores for the webapps and Environment Manager. When I restarted EV the agents weren't managing to communicate with the EV Server. TS advised a solution to this, which was to remove the agent data directory and start using the command line rather than Windows Service Manager as per KB52668:   config\Lev1\Web\SASEnvironmentManager\agent-5.8.0-EE\bin\hq-agent.bat start   This worked. There were various messages which appeared after the command was run:   wrapper | Starting the SAS [config-Lev1] SAS Environment Manager Agent service... wrapper | Waiting to start... wrapper | SAS [config-Lev1] SAS Environment Manager Agent started. [ Running agent setup ] Should Agent communications to HQ be unidirectional [default=no]: yes What is the HQ server IP address: server.domain Should Agent communications to HQ always be secure [default=yes]: Yes What is the HQ server SSL port [default=7443]: 7443 - Testing secure connection ... Success What is your HQ login [default=hqadmin]: sasevs@saspw What is your HQ password: **Not echoing value** What is the agent IP address [default=***.***.***.***]: server.domain - Received temporary auth token from agent - Registering agent with HQ - HQ gave us the following agent token 1654862220270-8565811125738354432-5097207690335336169 - Informing agent of new HQ server - Validating - Successfully setup agent - Agent using new transport, unidirectional=true, port=7443   So my question is, what's the difference between running the command line and stopping/starting with Service Manager? TS weren't able to say. Thanks. ... View more

SAS 9.4M7 on Windows 2012 R2 I'm at the point of renewing certificates on our mid-tier server and have a certificate bundle ready. However, it needs exported to PKCS12 format for the webapps. I've been following the procedure that we've used before but I'm getting an error with the openssl command:   C:\Windows\system32>Set OPENSSL_CONF= E:\SAS\sashome\SASWebServer\9.4\httpd-2.4.27.1-64\ssl\openssl.cnf C:\Windows\system32>e: E:\>cd E:\SAS\sashome\SASWebServer\9.4\httpd-2.4.27.1-64\bin E:\SAS\sashome\SASWebServer\9.4\httpd-2.4.27.1-64\bin>openssl pkcs12 -export -chain -inkey "E:\SAS\config\Lev1\Web\WebServer\ssl\keyfile.key" -in "C:\temp\Certificates\certfile.crt" -name hq -CAfile "C:\temp\Certificates\CAchain.crt" -out c:\temp\Certificates\tcServer.p12 19040:error:0200107B:system library:fopen:Unknown error:.\crypto\bio\bss_file.c:175:fopen(' E:\SAS\sashome\SASWebServer\9.4\httpd-2.4.27.1-64\ssl\openssl.cnf','rb') 19040:error:2006D002:BIO routines:BIO_new_file:system lib:.\crypto\bio\bss_file.c:184: 19040:error:0E078002:configuration file routines:DEF_LOAD:system lib:.\crypto\conf\conf_def.c:203: I tried adding the path to the openssl command to PATH, to no avail. The certificate file is just that, ie. doesn't include the CA chain. The CA file just contains the root and intermediate certificates. I seem to have problems with this every time, and no matter how well I document the process it always goes wrong! Suspect this might be a job for TS but just in case anyone can help?    ... View more

I'm trying to find out if there is a way to open OneDrive locations in SAS Studio Enterprise Edition (3.81). To be clear, I'm wanting to be able to gain access to programs, flows (.cpf files) and so on, rather than read and write data programmatically. The background to this is that, as an organisation, we currently have users' documents folders redirected to shared drives, mapped as their H: drives. But these are going to be shut down soon and users are being told to move files either to our document management system or OneDrive folders. In SAS Studio I have been able to create a folder shortcut to my H: drive just by using its UNC. But I can't see a way to do the equivalent with OneDrive. I've had a look at @ChrisHemedinger's webinar on using SAS with Microsoft 365 but that's more about data, and anyway, I am not authorised to register apps in Azure. As an aside, I can see how this could actually be useful as well, for reading/writing data, so I will probably pursue it with our admins. Thanks. ... View more