I executed againg the query using the sastrace option. Follows the results: 024-03-08T14:06:39,961 INFO [00000009] :user - 27 options sastrace=',,,d' sastraceloc=saslog msglevel=i; 2024-03-08T14:06:39,961 INFO [00000009] : user - 28 2024-03-08T14:06:39,967 INFO [00000015] : user - 29 proc sql ; 2024-03-08T14:06:39,967 INFO [00000015] : user - 30 connect to bigquery as perm (project='aa-tedm-dtm' credfile='/files/access/bq/tedm-dtm.json' 2024-03-08T14:06:39,967 INFO [00000015] : user - 31 schema='aa-base-prd'); 2024-03-08T14:06:41,765 INFO [00000015] : user - 2024-03-08T14:06:41,766 INFO [00000015] : user - 32 Create table teste as 2024-03-08T14:06:41,766 INFO [00000015] : user - 33 select * from connection to perm 2024-03-08T14:06:41,766 INFO [00000015] : user - 34 (select * from aa-base-prd.analytics.table_2 ); 2024-03-08T14:06:42,412 INFO [00000015] : user - 0 1709917602 no_name 0 SQL (2) 2024-03-08T14:06:42,412 INFO [00000015] : user - SASGBQ_1: Prepared: on connection 0 1 1709917602 no_name 0 SQL (2) 2024-03-08T14:06:42,413 INFO [00000015] : user - select * from aa-base-prd.analytics.table_2 2 1709917602 no_name 0 SQL (2) 2024-03-08T14:06:42,413 INFO [00000015] : user - 3 1709917602 no_name 0 SQL (2) 2024-03-08T14:06:43,951 INFO [00000015] : user - 4 1709917603 no_name 0 SQL (2) 2024-03-08T14:06:43,951 INFO [00000015] : user - SASGBQ_2: Executed: on connection 0 5 1709917603 no_name 0 SQL (2) 2024-03-08T14:06:43,951 INFO [00000015] : user - Prepared statement SASGBQ_1 6 1709917603 no_name 0 SQL (2) 2024-03-08T14:06:43,951 INFO [00000015] : user - 7 1709917603 no_name 0 SQL (2) ... View more

Thanks, it’a because I access a project that it’s empty, it’s only for the connection (for billing purposes). After I connect in this first project, I need to access the table that is located in other project and schema. Do you know which Google permission the services account needs to query from SAS ? The user will not save anything in Google, only access the data. ... View more

So, I tríed to use libname instead of SQL pass-through but it’s not working for the structure inside GCP.    The user has access to a project id and once on it, he connect to other project id, schema and table. In SQL pass-through I can configure this type of access, defining the project  id and schema on the connection and then in the FROM I can use project_id2.schema2.table. There is any to use LIBNAME if I had this structure en GCP? ... View more

Hi guys,    After some tries, we connected using PBI desktop but not PBI Gateway (personal mode). The string is the same, but in PBI gateway request again the credentials and timeout occur. We found this Microsoft note, but even when selecting anonymous authentication the error persists.    String:   provider=sas.IOMProvider.9.44;data source='iom-name://SASApp - Logical Workspace Server";sas cell cache size=10000;sas machine dns name=XXXXX;sas port=8591;sas protocol=2;sas server type=1;sas metadata user id=YYY;sas metadata password=ZZZZ;sas metatada location:RRRRRR:8561     Regards, ... View more

Thanks! Added the WORK as indicated and now works fine.    Regards,  ... View more

@MarcoGhiglieri , you are right. I was looking at the general MetadataServer log. So, I verified the log of metadata for today and now I'm seeing a different error:   2023-07-05T11:53:28,960 ERROR [00000005] :sas - Unable to obtain IP addresses for host sasdev. ... View more

It's very strange, @MarcoGhiglieri .   Yes, the return of date command is: Wed Jul 5 13:24:26 GMT 2023 In fact, in the setinit log appears ok too: 1 The SAS System 12:58 Wednesday, July 5, 2023 NOTE: Copyright (c) 2016 by SAS Institute Inc., Cary, NC, USA. NOTE: SAS (r) Proprietary Software 9.4 (TS1M7) Licensed to XXXXXXXXXXX, Site 0000000. NOTE: This session is executing on the Linux 4.1.12-124.48.6.el6uek.x86_64 (LIN X64) platform. ... View more

Hi @MarcoGhiglieri ,   Yes, the Foundation looks fine, but the problem is exactly the update SID for Metadata. If we tried to execute option 6 from SAS Deployment Manager, we have an error saying the MetadataServer is not up or running.   So, when we tried to start the metadata server using the metadataserver.sh script, we received the following error: Waiting up to 600 seconds for Metadata Server to listen to port 8561. Server is started (pid 7176)... Server is stopped Log files are located at: /sas/config/Lev1/SASMeta/MetadataServer/Logs   And the log for the metadata services is: ERROR: includes SETINIT information. ERROR: Initialization of setinit information from SASHELP failed. ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED. ERROR: Unable to initialize the SAS kernel. ERROR: The current date of Tuesday, May 23, 2023 is past the final expiration date for your SAS system, which is Tuesday, March 1, 2022. Please contact your SAS Installation Representative to obtain your updated SAS Installation Data (SID) file, which ERROR: includes SETINIT information.   So, at this moment we have the SAS Foundation ok but we can't find a way to update the SID on metadata.  ... View more