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

Thanks @Kurt_Bremser .    As mentioned, we have one server only, it's Linux with SAS 9.4M7 installed. So, as you mentioned, we run the following command: /sas/software/SASFoundation/9.4/sas sas -setinit /sas/setinit.sas   After that, we verified the log and the setinit procedure executes fine. Then, we tried to start the MetadataServer by running the following command: /sas/config/Lev1/SASMeta/MetadataServer/MetadataServer.sh start   But the same error occurs:   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   When we validated the log file, the error appears:   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.   The setinit file we are using is: Site validation data before saving/zapping Current version: 9.04.01M7P080620 Site name: 'XXXXXXXXXX'. Site number: 00000000000. CPU A: Model name='' model number='' serial=''. Expiration: 29NOV2023. Grace Period: 45 days (ending 13JAN2024). Warning Period: 45 days (ending 27FEB2024). System birthday: 02FEB2023. Operating System: LIN X64 . Product expiration dates: ---Base SAS Software 29NOV2023 (CPU A) ---SAS/STAT 29NOV2023 (CPU A) ---SAS/GRAPH 29NOV2023 (CPU A) ---SAS/ETS 29NOV2023 (CPU A) ---SAS/OR 29NOV2023 (CPU A) ---SAS/AF 29NOV2023 (CPU A) ---SAS/IML 29NOV2023 (CPU A) ---SAS/SHARE 29NOV2023 (CPU A) ---SAS/CONNECT 29NOV2023 (CPU A) ---SAS/SHARE*NET 29NOV2023 (CPU A) ---SAS Risk Management 29NOV2023 (CPU A) ---SAS Enterprise Miner 30MAY2023 (CPU A) ---SAS Risk Management-Enterprise Edition 29NOV2023 (CPU A) ---External function linking system 29NOV2023 (CPU A) ---SAS Integration Technologies 29NOV2023 (CPU A) ---SAS/Secure 168-bit 29NOV2023 (CPU A) ---SAS Enterprise Miner Server 30MAY2023 (CPU A) ---SAS Enterprise Miner Client 30MAY2023 (CPU A) ---SAS Credit Scoring 30MAY2023 (CPU A) ---SAS High-Performance Forecasting 29NOV2023 (CPU A) ---SAS Enterprise Guide 29NOV2023 (CPU A) ---OR OPT 29NOV2023 (CPU A) ---OR PRS 29NOV2023 (CPU A) ---OR IVS 29NOV2023 (CPU A) ---OR LSO 29NOV2023 (CPU A) ---SAS/ACCESS Interface to Oracle 29NOV2023 (CPU A) ---SAS/ACCESS Interface to PC Files 29NOV2023 (CPU A) ---SAS/ACCESS Interface to ODBC 29NOV2023 (CPU A) ---SAS/ACCESS Interface to R/3 29NOV2023 (CPU A) ---SAS/IML Studio 29NOV2023 (CPU A) ---SAS Workspace Server for Local Access 29NOV2023 (CPU A) ---SAS Workspace Server for Enterprise Access 29NOV2023 (CPU A) ---SAS/ACCESS to Postgres 29NOV2023 (CPU A) ---SAS Firmwide Risk Management for Insurance 29NOV2023 (CPU A) ---High Performance Suite 29NOV2023 (CPU A) ---SAS Add-in for Microsoft Excel 29NOV2023 (CPU A) ---SAS Add-in for Microsoft Outlook 29NOV2023 (CPU A) ---SAS Add-in for Microsoft PowerPoint 29NOV2023 (CPU A) ---SAS Add-in for Microsoft Word 29NOV2023 (CPU A) ---SAS High-Performance Risk Engine Server 29NOV2023 (CPU A) ---SAS Search and Indexing Server 29NOV2023 (CPU A) ---SAS Web Crawler Server 29NOV2023 (CPU A) ---Business Rules Services 29NOV2023 (CPU A) ---SAS LASR Analytic Server 29NOV2023 (CPU A) ---SAS Visual Analytics Hub 29NOV2023 (CPU A) ---SAS Visual Analytics Services 29NOV2023 (CPU A) ---High Performance STAT MPP 29NOV2023 (CPU A) ---Decision Manager Server 29NOV2023 (CPU A) ---Advanced Programming for LASR Analytic Server 29NOV2023 (CPU A) ---High Performance Analytics Distributed Mode 29NOV2023 (CPU A) ---SAS Visual Analytics Server Components 29NOV2023 (CPU A) ---Bus Rules Manager Server 29NOV2023 (CPU A) ---Stress Testing Server 29NOV2023 (CPU A) ---Visual Analytics Explorer 29NOV2023 (CPU A) ---Model Imp Mgmt Server 29NOV2023 (CPU A) ---Model Implement Pltfrm Adv 29NOV2023 (CPU A) ---SAS/ACCESS to Google BigQuery 29NOV2023 (CPU A) NOTE: Siteinfo data have been updated. I also open a SAS Ticket (7613820055). ... View more

Hi @huntdoug,    Thanks so much. The track number is 7613759108. The support asked to delete all the logs and restart the services. We did it yesterday and upload the logs and the results of proc setinit and proc product_status.    Some additional details, we restore the environment to last week's image (when everything works) but the error is the same. We requested if it's possible, an alternative or temporary SAS license to validate if something is wrong with our SID file but we don't have any answer now.   If TechSupp needs to connect with our environment, using WebEx or similar, we are totally available.  ... View more

Thanks, @StefanM    Still not working...   ... View more

Hi @StefanM ,   Nope, same thing:    [sas@sas bin]$ sh -xv /sas/software/SASWebApplicationServer/9.4/tcruntime-ctl.sh SASServer1_1 status #!/bin/sh # ------------------------------------------------------------------------------ # Copyright (c) 2021 by SAS Institute Inc., Cary, NC USA 27513 # ------------------------------------------------------------------------------ # # Invoke Tomcat's catalina shell script to control the web application server. # # ------------------------------------------------------------------------------ # Read the instance name if [ "$#" -gt 0 ]; then name=$1 shift else echo "Invalid sytax." exit 1 fi + '[' 2 -gt 0 ']' + name=SASServer1_1 + shift # Read the command if [ "$#" -gt 0 ]; then command=$1 shift else echo "Invalid sytax." exit 1 fi + '[' 1 -gt 0 ']' + command=status + shift # Read the path to the instance if [ "$#" -gt 1 ]; then if [ "$1" = "-n" ]; then # Shift off the recognized command switch shift # Remember and shift off the template name instancedir=$1 shift else echo "Invalid syntax." exit 1 fi else echo "Invalid sytax." exit 1 fi + '[' 0 -gt 1 ']' + echo 'Invalid sytax.' Invalid sytax. + exit 1 ... View more