<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Studio failing to load on new installation for non-admin users in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Studio-failing-to-load-on-new-installation-for-non-admin-users/m-p/614197#M17936</link>
    <description>&lt;P&gt;So turns out this was something relatively trivial, but not obvious from the errors: I had forgotten to set the default ACT to allow our custom group permission to do anything (including read metadata, I'm guessing being the issue here).&amp;nbsp; Oops.&amp;nbsp; Fixing that made this go away.&lt;/P&gt;</description>
    <pubDate>Sat, 28 Dec 2019 07:39:11 GMT</pubDate>
    <dc:creator>snoopy369</dc:creator>
    <dc:date>2019-12-28T07:39:11Z</dc:date>
    <item>
      <title>Studio failing to load on new installation for non-admin users</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Studio-failing-to-load-on-new-installation-for-non-admin-users/m-p/614086#M17923</link>
      <description>&lt;P&gt;I just set up a one-machine Office Analytics server (9.4 TS1M6, not Viya), and must have missed something, but can't figure out what.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I log on to SAS with my admin account, it works correctly - can load Studio, run code, etc.&amp;nbsp; But when I log on to SAS with my non-admin account, I get a 500 error from Studio, no actual load of Studio, and this in the SAS Studio log:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;[tomcat-http--23] ERROR [unknown] org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASStudio].[coderServlet] - Servlet.service() for servlet [coderServlet] in context with path [/SASStudio] threw exception&lt;BR /&gt;java.lang.RuntimeException: Unable to create a user context for user: xxxuseridxxx@xxxadgroupxxx&lt;BR /&gt;at com.sas.svcs.authorization.impl.MetadataUserDetailsServiceWrapper.loadUserByUsername(MetadataUserDetailsServiceWrapper.java:147)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Metadata server log is clean (it shows the log in successfully).&amp;nbsp; I assume I must have missed something related to user access, but can't figure out what...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I initially thought it was due to the server team not adding LogOnAsBatch permissions to the user group we manage server access with, but they fixed that and it's still occurring.&amp;nbsp; I checked that the SAS Work folder has the right permissions (full control: folder only).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any thoughts on what I should check next?&amp;nbsp; What logs should I be looking at for more information?&amp;nbsp; Will adding trace/debug level to Studio help here?&amp;nbsp; I don't think the SAS session is ever actually created, so I don't have a SAS log available to look at (unless I'm missing something) - nothing in \temp\SASStudioSessions anyway.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 27 Dec 2019 14:40:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Studio-failing-to-load-on-new-installation-for-non-admin-users/m-p/614086#M17923</guid>
      <dc:creator>snoopy369</dc:creator>
      <dc:date>2019-12-27T14:40:19Z</dc:date>
    </item>
    <item>
      <title>Re: Studio failing to load on new installation for non-admin users</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Studio-failing-to-load-on-new-installation-for-non-admin-users/m-p/614197#M17936</link>
      <description>&lt;P&gt;So turns out this was something relatively trivial, but not obvious from the errors: I had forgotten to set the default ACT to allow our custom group permission to do anything (including read metadata, I'm guessing being the issue here).&amp;nbsp; Oops.&amp;nbsp; Fixing that made this go away.&lt;/P&gt;</description>
      <pubDate>Sat, 28 Dec 2019 07:39:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Studio-failing-to-load-on-new-installation-for-non-admin-users/m-p/614197#M17936</guid>
      <dc:creator>snoopy369</dc:creator>
      <dc:date>2019-12-28T07:39:11Z</dc:date>
    </item>
  </channel>
</rss>

