I am guessing you are checking the operating system user id? Perhaps you could show a code fragment where you are checking it. The operating system user id would be a shared identity when using SAS Token Authentication. When you say admin username are you talking about the spawned servers identity (often named sasrv)? The SAS metadata identity should still be available to stored processes to query and use and should represent the identity of the person who authenticated to the SAS platform (rather than the operating system process owner of the SAS stored process server instance). If you haven't already seen it, have a look in the SAS(R) 9.4 Stored Processes: Developer's Guide, Second Edition particularly the section Using Reserved Macro Variables. What do you get when you %put the following macro variables in your stored process? &_AUTHTYP &_METAPERSON &_METAUSER &_RMTUSER &_SECUREUSERNAME &_USERNAME ... View more

Hi Patrick, Sorry for the confusion, that blog post must have been written before SAS 9.4 was released. That plug-in is certainly supported for use with SAS 9.4 and I use it extensively (it is also completely read-only at this point). The page https://www.metacoda.com/en/metacoda-security-plug-ins/sysreqs/ shows the SAS versions supported - essentially everything beyond SAS 9.2 I'll update the old blog post to indicate SAS 9.4 support. We did that metadata explorer search before the Search tab became available in SAS Management Console and we kept it afterwards because we still needed to search beyond public types in situations like this (and we still support older SAS versions that don't have the Search tab). I mentioned V-lengths because, the way XMLSELECT works with V-lengths, you'll only be able to find the code fragment if it occurs fully within the first text page. I found this when searching for stored process code in metadata. In that particular case the SP code was in TextStore with a V-length of 1000 and so I could only find code fragments (using XMLSELECT) if the fragment occurred within the first 1000 characters of the SP code in metadata. To search beyond the V-length requires extracting metadata and searching outside of the metadata server. Cheers Paul ... View more

Have a look at SAS Usage Note 49421 - A "Cannot write image" error might occur with ODS Graphics and the SAS/GRAPH® Statistical Graphics (SG) procedures You need to specify a location in your ODS statements to point to a directory where you have write permissions. Without this it will be attempting to write to the default directory, which for a shared SAS platform environment will be the application servers configuration directory (e.g. /opt/sas/config/Lev1/SASApp). I know it probably doesn't sound like it, but in a way it's good that you are getting this error. It suggests that file system permissions on your SAS server might have been configured well. Without them the SASApp directory can get littered with lots of temporary files. ... View more

It sounds like you might be after the same sort of permission pattern as one might want for folders that house home directories (automatically created ones). i.e. where a user can create a folder which then becomes available only to them (+ admins and system). If so, have a look at this pattern: NTFS Permissions for root share that houses Home Directories Windows Server 2008 R2 - Server Fault ... View more

As I mentioned, did you get anything in the work.mduimplb_failedobjs table after running %mduimplb? This will provide information on any failed metadata updates. If you are able to post the SAS log (zipped up) that would be helpful to look at. Also earlier in this thread you were getting the odd error "ERROR: login : Foundation cannot be found in the  container in the  repository." How did you rectify that and what was the cause? I'm wondering if it might be related. ... View more