Hi Len,
You mentioned you checked the permissions on the library and they had full read write access. Which library did you check and which permissions were you checking? Did you check the Secured Library object or a traditional SAS Library object? For the Secured Library were you looking at the additional permissions: Create Table, Alter Table etc. Also, how are you assigning the library - is the base engine being used directly or are you using the Metadata Libname Engine with the METAOUT option?
From the error message you posted, and the fact that you didn't have any problems as an administrator, I was thinking it looked like it could be an issue with the permissions on the Secured Library object. There is more info on the permission requirements for this in the Permissions for Metadata-Bound Data section of the SAS 9.4 Guide to Metadata-Bound Libraries (and several other sections too). To add a Secured Table to a Secured Library the Create Table permission is required (Alter Table when overwriting an existing table). Interestingly WriteMetadata is not required on the Secured Library (as it is in many other instances when linking a new object to an existing object). However, when I just I tested a missing Create Table permission I got a different (and very helpful) error message (in SAS 9.4 M4):
NOTE: Metadata-bound library permissions are used for SECLIB.TABLE.DATA.
ERROR: USERID as Identity Name is not authorized to create data set SECLIB.TABLE.DATA. Create Table permission is required.
So unless the error message has changed between M2 and M4 it doesn't look like this is the issue. I'll still post this comment though just in case it's useful to others who read this thread in future. 🙂
It would probably be worth sending this one on to SAS Technical Support if you haven't done so already.
Cheers
Paul
... View more
![SASGF 2020 [Virtual] Attendee](/html/@A53A708409112314CE528E074D4C8C1F/badge_icons/badge_sasgf20_attendee.png "SASGF 2020 [Virtual] Attendee"){kind=icon}
