BookmarkSubscribeRSS Feed
shoin
Lapis Lazuli | Level 10

Environment:

SAS 9.4 TS1M7 WIN server, 3 machine plus clients

Two non-preassigned sql DB libraries that are using a service ID and PWD for connecting to sql db.  A SQLAuth was established, and a group was set sql_users_grp and login was assigned to it.

Issue:

EG those two libraries do not appear for one end user, userX

Troubleshooting and Checks:

  1. UserX could see the said 2 sql DB libraries in SMC
  2. UserX could run a libname statement and establishes connection, all registered tables appear in an EG session, table could be selected and loaded.
  3. There is no Extended attribute defined
  4. UserX is member of the sql_users_grp
  5. SAS Folder location both have sql_users_grp added and have RM, R, W, WMM
  6. SQL Libraries themselves have RM, R, W, WMM for the sql_users_grp and SASUSERS has RM,R
  7. Workspace server, STP, Pooled WSS all have SASUSERS appropriate permission
  8. In SAS EG, all default SASApp-* data libraries, SASHELP, WRSTEMP, etc. all libraries appear, except the two SQL DB libraries.
  9. Checked AD group membership, UID verification all access is as expected
  10. This user except some CI admin access has the same group membership as I (author) have, I have no issue viewing the two SQL DB libraries in SMC and EG.
  11. Access to the two DB schemas was verified.

 

Stumped why these two libraries not appear in SAS EG session, however they are accessible via libname statement, in SMC (same user) ... 🤔

 

Thank you in advance,

 

S

6 REPLIES 6
SASKiwi
Opal | Level 21

Please post the LIBNAME statement that works. There must be some difference between that and how you are defining the same library in SMC.

 

shoin
Lapis Lazuli | Level 10
We used the DISPLAY LIBNAME value copied it and ran in a BASE editor session as well as EG session.
SASKiwi
Opal | Level 21

But what was the outcome? We can't help you if you say you did something without posting the result.

 

Please post the SAS log of the LIBNAME you ran. Also if it assigned without any error, post a screenshot of the EG Server list window showing the created library in expanded mode.

Jackie_sas
SAS Employee
Check the Assign tab of the library properties in SAS Management Console and make sure a server is assigned. This makes the library available to the server and makes the library visible to users of the server. Enterprise Guide only shows libraries that are assigned to the server. Even though SAS Management Console says the is assignment is optional, it is recommended to always assign a server to a library.
shoin
Lapis Lazuli | Level 10
SASApp server is assigned.
shoin
Lapis Lazuli | Level 10
Update

I enabled the EG Client side log. I see that the EG routine finds these libraries but then they do not appear for this user. I hope somehow Chris H. gets to see this
--- begin ---
2021-10-21 12:58:42,888 [9] DEBUG SAS.EG.SDS.Model.SDSCollectionBase [(null)] - SDS-START:100012:Obj 179:DoClear():SDSCollectionBase.cs@365: Clearing collection: [Collection 'Libraries', Item Type = 'SAS.EG.SDS.Model.Library', ObjectID =179], Events = False, itemType = SAS.EG.SDS.Model.Library, Status is Populated
2021-10-21 12:58:42,889 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-START:100013:Obj 235:ClearWithoutEvents():LibraryState.cs@859: Clear library 'CIExports'
2021-10-21 12:58:42,890 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-LOG :Obj 235:ClearWithoutEvents():LibraryState.cs@864: Clearing all AssignedStateMap entries for library CIExports.
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-START:100014:Obj 235:ClearWithoutEvents():LibraryState.cs@866: AssignedStateMap: In Use: Iterate over collection and use each entry.
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-LOG :Obj 235:ClearWithoutEvents():LibraryState.cs@870: Clearing datasets collection objID=237
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.SDSCollectionBase [(null)] - SDS-START:100015:Obj 237:DoClear():SDSCollectionBase.cs@365: Clearing collection: [Collection 'Datasets', Item Type = 'SAS.EG.SDS.Model.Dataset', ObjectID =237], Events = False, itemType = SAS.EG.SDS.Model.Dataset, Status is NotPopulated
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.SDSCollectionBase [(null)] - SDS-END :100015:Obj 237:DoClear()
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-END :100014:Obj 235:ClearWithoutEvents()
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-END :100013:Obj 235:ClearWithoutEvents()
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-START:100016:Obj 231:ClearWithoutEvents():LibraryState.cs@859: Clear library 'CISQLJDE'
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-LOG :Obj 231:ClearWithoutEvents():LibraryState.cs@864: Clearing all AssignedStateMap entries for library CISQLJDE.
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-START:100017:Obj 231:ClearWithoutEvents():LibraryState.cs@866: AssignedStateMap: In Use: Iterate over collection and use each entry.
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-END :100017:Obj 231:ClearWithoutEvents()
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-END :100016:Obj 231:ClearWithoutEvents()
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-START:100018:Obj 233:ClearWithoutEvents():LibraryState.cs@859: Clear library 'CISQLMCD'
2021-10-21 12:58:42,891 [9] DEBUG SAS.EG.SDS.Model.LibraryState [(null)] - SDS-LOG :Obj 233:ClearWithoutEvents():LibraryState.cs@864: Clearing all AssignedStateMap entries for library CISQLMCD.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 6 replies
  • 405 views
  • 0 likes
  • 3 in conversation