About RGUL

RGUL · ‎01-15-2015

Thanks for the explanation from both Sheila and Jaap. It has helped me understand how the Roles and metadata access relate to each other. When you say ' anyone authenticating to the metadata server', I assume you mean anyone who has an OS level identity on the SAS metadata server. This is in contrast to someone how has a SAS Metadata identity itself (one that is defined using SMC). Is this correct? SAS documentation appears to associate multiple meanings to the term Metadata server, and metadata, that it can get very confusing. Thanks.

RGUL · ‎01-15-2015

I identified the problem as setuid not being set on our metadtaa server to change permissions on elssrv, sasperm and sasauth on our metadata server. Once that was fixed, I was able to use my regualr account to log into SMC. Thanks for your help in pointing me to sasauth.

RGUL · ‎01-14-2015

Thanks for the explanation. I incorrectly referred to PUBLIC as a User. So from your comments, I infer that by granting PUBLIC any role, the system is in effect preventing PUBLIC access to metadata,to an individual who does NOT have a SAS identity. This is because PUBLIC's authorization level is DENY for both Read and Write metadata. Is this understading correct ? Thanks.

RGUL · ‎01-13-2015

When I try to start SMC and enter an Id and password for an entity that has a SAS identity and is the SAS Administrators group, I get an error 'Unable to launch authentication utility . The application could not log on to the server myservername:8591' When I use internal id sasadm (sasadm@saspw) at the log in window for SMC, I am logged into SMC with no problems. The log /Lev1/Logs/SASMeta_MetadataServer_yyyy-mm-dd.log has the following lines: INFO[number]: Unable to launch authentication utility. WARN [number] : New Client connection (12345) rejected from server port 8561 for user xxxxx. Peer IP address and po rt are (:ffff:99:999:99:99):99999 Client connection 12345 closed Our metadataserver is on Linux and I connect to the server via using Remote Desktop Protocol from my workstation, and execute SASMC from the linux command line. Thanks.

RGUL · ‎01-12-2015

USI noticed that out of the box implementation, has the SAS delivered rold of Add-in for Microsoft Office: Advanced properties having one member - which is the user 'PUBLIC'. Why does SAS provide PUBLIC user access to the Advanced Properties role, rather than the OLAP or Analysis role? Does SAS recommend that users in general be given the Advanced role, rather than the 'Analysis' or 'OLAP' variations? Thanks

RGUL · ‎01-08-2015

Thanks. I've marked it answered.

RGUL · ‎01-07-2015

A SAS consultant had instructed us to make the change in the sasnev_local file in SASHOME/SASFoundations/9.3/bin folder. I realized I should have done the checksum validation before I made the change in the file, as the validation was to confirm the install was completed corectly. The error disappeared once I reverted the sasenv_local to its original state,before running the Deployment Tester suite of tests for SAS IQ.

RGUL · ‎12-31-2014

I did not choose to run SAS IQ after SAS OQ. The Deployment Tester did it in that sequence when I selected to execute the full suite of tests. So does this error happen for everyone ? With regard to file contents being changed, as per the documentation on configuration tasks to be done after install (see document http://support.sas.com/documentation/installcenter/en/ikfdtnurnxcg/64205/PDF/default/config.pdf) I had to make changes in sasenv_local in /SASROOT/SASFoundations/9.3/bin to add the LIBNAME statements. In short is this error not severe enought to warrant fixing before proceeding with the rest of the install/configuration? Thanks.

RGUL · ‎12-31-2014

New installation of SAS 9.3. I have finished the Install and Configure steps using SAS Deployment Wizard, and am now doing the post configuration steps which involve validation etc. from SAS Management Console.

RGUL · ‎12-30-2014

One of the steps in the post installation activities on the Compute server (as per the 'Instructions.html' document) is to run validation tests using SAS Management Console, and to run the Deployment Tester suite of tests from SAS Management Console. The Deployment Tester suite checked out ok on all but the SAS IQ test which had 1 failure, when it found a checksum error in sasenv_local. Why did this checksum error happen, and what needs to be done to fix it? Thanks.

RGUL · ‎12-17-2014

Is it possible to list multiple recipients for alert email from SAS Metadata server? We are told to list the recipient in the file Lev1/SASMeta/MetadataServer/omaconfig.xml. The entry in omaconfig.xml is coded as ALERTEMAIL="recipientEmailID@emailserver" If multiple recipients are possible, what is the syntax to be used - - would it be "emailID1@server1,"emailID2@server2" or would it be "email1@serverID1, emailID2@server2" ? Thanks

RGUL · ‎12-17-2014

Thank you Kurt and Linus. From your responses I gather that the recommended approach is to do the orderly shutdown restart - shutdown sequence - SAS services on midtier, compute, metadata servers, then followed by restart in the reverse order.

RGUL · ‎12-15-2014

If the instructions are to make a change to a configuration file, and then stop and start the metadata server in order for the change to become effective, do I need to first - stop ALL SAS services and JBOSS services on Midtier - then stop all SAS services on Compute sever - then stop all SAS services on Metadata server before I - start all SAS services on Metadata server - then start all SAS sevices on Compute server - then start all SAS and JBOSs services on Midtier Server? Or can I just stop and start all SAS services on Metadata server? For a similar need on Compute server, would I need to first stop all services on Midtier, then Compute, then start on Compute and then Midtier ? (don't stop and start on Midtier). OR, do I just need to stop and start on Compute server? However, on Midtier servier, I would just need to stop and start services on Midtier server. Of course, all users will need to be logged off, etc. Thanks.

RGUL · ‎12-08-2014

Thank you Juan and Andrew for helping to clarify why 32 and 64 bit versions are getting installed and about the preference and advisability of using the 32 bit version.

RGUL · ‎12-02-2014

Actually, our current implementation, when I check Start/programs/SAS, i see both 32 and 64 bit options. Is it possible to have both versions, if EG was only installed once?

Online Status	Offline
Date Last Visited	‎09-01-2015 07:11 AM

Re: By default, why is Public listed as a member of Role Add-in for Mi...

Re: Unable to log into SMC with user id other than sasadm@saspw.

Re: By default, why is Public listed as a member of Role Add-in for Mi...

Unable to log into SMC with user id other than sasadm@saspw.

By default, why is Public listed as a member of Role Add-in for Micros...

Re: Checksum error in sasenv_local found by Deployment Tester suite of...

Re: Checksum error in sasenv_local found by Deployment Tester suite of...

Re: Checksum error in sasenv_local found by Deployment Tester suite of...

Re: Checksum error in sasenv_local found by Deployment Tester suite of...

Checksum error in sasenv_local found by Deployment Tester suite of tes...

Re: By default, why is Public listed as a member of Role Add-in for Mi...

Re: Unable to log into SMC with user id other than sasadm@saspw.

Re: By default, why is Public listed as a member of Role Add-in for Mi...

Unable to log into SMC with user id other than sasadm@saspw.

By default, why is Public listed as a member of Role Add-in for Micros...

Re: Checksum error in sasenv_local found by Deployment Tester suite of...

Re: Checksum error in sasenv_local found by Deployment Tester suite of...

Re: Checksum error in sasenv_local found by Deployment Tester suite of...

Re: Checksum error in sasenv_local found by Deployment Tester suite of...

Checksum error in sasenv_local found by Deployment Tester suite of tes...

multiple recipients for alert emails set in omaconfig.xml file?

Re: What needs to be done to stop and start metadata server - SAS 9.3 ...

What needs to be done to stop and start metadata server - SAS 9.3 M1

Re: How can one identify if SAS Enterprise Guide is installed in 32-bi...

Re: How can one identify if SAS Enterprise Guide is installed in 32-bi...