Here's an example entry from our metadata logs (suitably edited):   2025-01-09T16:36:16,945 INFO [31155358] 1567886:zzzzzzz@Dddddddd - Audit Public Object Type=User Name=XXXXXXXXXX ObjId=OOOOOOOO.AAAAAAA has been delete ... View more

I think this could be a case for Tech. Support. We've had problems with the cache locator before and they've always been able to resolve them. ... View more

It's a few years old but I think this probably answers your question: Solved: I have a user asking if SAS 9.4 m7 will run on a Surface Pro X, with a... - SAS Support Communities ... View more

I don't think you'll get the scheduled jobs from the metadata logs, only entries where people are logging in to the metadata server (and filtering on "APPNAME=SASManagementConsole" will give you the users who have done this with SMC). I see from a later reply that you're using Operating System Services as your scheduler so for scheduled tasks you'd maybe need to look at logs within <config>/Lev1/SchedulingServer. In Windows there's a directory structure here of <username>\<jobname> with logs created by the job's VB Script. I don't know if that helps? Or, the actual SAS programs run under the Batch Server, so there are SAS logs in <config>/Lev1/SASApp/BatchServer/Logs. Alternatively, I'm not knowledgeable enough about Unix to know if there are logs created by cron? Might be entries in syslog? ... View more

You can't view the logs from SMC. You have to log onto the server(s) to do so. For the metadata server logs, these will commonly be in <config>/Levx/SASMeta/MetadataServer/Logs on the metadata server and for the object spawner logs, <config>/Levx/ObjectSpawner/Logs on the compute server.   When @LinusH asks about the scheduler, SMC is only the front end to this. Behind the scenes it will be relying on specific scheduling software. It could be Platform Suite for SAS if you have that licensed or the operating system scheduler on your servers (ie. cron on Unix or Linux, or the Task Scheduler on Windows). Here's where you set that in SMC:   ... View more

For SMC check the metadata server logs. Look for entries with "APPNAME=SASManagementConsole " For EG users I don't think the metadata logs will tell you if an actual SAS session has been started, only if they've connected to the metadata. You could get active users from the Object Spawner logs (that's what I do). ... View more

It's worth trying the SASTRACE system option to see what is actually being sent and received via ODBC: SAS Help Center: SASTRACE= SAS System Option     ... View more

It's worth trying a special catalog query as you're using ODBC. Something like:   PROC SQL; connect to odbc as dbrk (dsn="dbrk" user="clinet-id" password="password" ); select * from connection to dbrk ( ODBC::SQLTables(,,,) ); disconnect from dbrk; quit; This should list all tables in all schemas to which you have access.   More information: SAS Help Center: SQL Pass-Through Facility Specifics for ODBC ... View more

Still working on it. I had to remove and re-install the IR Studio service to get it running, but the SASSearchService on the mid-tier is not detecting it. TS are investigating for me. ... View more

If you're doing a full migration my guess is that the permissions would be retained. You may not have applied ACTs but there will be ACEs, either explicit or inherited. If you want to confirm this, examine the permissions on some of them. Here's an example of my own: You'll see all permissions are granted except WM, but including WMM. As I say, a full metadata migration will include everything (by definition), including all the access controls that are defined. If you want to dig into it further, the base SAS front-end has a very useful metadata browser in Tools, Accessories, or I believe Metacoda have a useful plugin to SASMC @MichelleHomes ? ... View more

Got a response from TS: The following steps are needed to update the SAS Information Retrieval Studio configuration to use a Python 3 instead of Python 2 version: 1) Stop SAS Information Configuration Studio by going to the <config>\Lev#\Applications\SASInformationRetrievalStudioforSAS directory and running:     IRStudio.bat stop    Note:  This can also be stopped from the Windows Services dialog. 2) Rename the <config>\Lev#\Applications\SASInformationRetrievalStudioforSAS\bin directory to bin-python2. 3) Copy the <SASHome>\SASInformationRetrievalStudioforSAS\1.57\StaticPy3\bin directory to the <config>\Lev#\Applications\SASInformationRetrievalStudioforSAS\ directory.  Note:  Your SASInformationRetrievalStudioforSAS may be different.  Replace 1.57 with the version you have.  4) Make a backup of the <config>\Lev#\Applications\SASInformationRetrievalStudioforSAS\IRStudio.bat file. 5) Modify the <config>\Lev#\Applications\SASInformationRetrievalStudioforSAS\IRStudio.bat file changing the PYTHON_EXEC to point to python where Python 3 is installed. For example, on my Windows test system, this is our setting:     Set PYTHON_EXEC="C:\Python38\python"   Save this change.  6) Start SAS Information Configuration Studio by going to the <config>\Lev#\Applications\SASInformationRetrievalStudioforSAS directory and running:     IRStudio.bat start   or restart this using the Windows Services dialog.   I'll report back when I've tried it.   ... View more

@JuanS_OCS wrote: A few greps on the files could tell you where to change things. Oh, I wish... (Windows!)   I think I may have to resort to TS in the end. ... View more

Many thanks @JuanS_OCS  I had referred to that documented note, based on which I reckoned it would be fairly easy. Although it seems to be saying to install the pywin32 module directly from a pypi host. This is something I can't do without a lot of hoop-jumping to allow access through our firewalls for the servers. I think there's probably a way to download the module and install it from a local drive though - I'll need to do some digging on that.   I suppose what I really wanted to know is what other configuration changes might be necessary, as I can't find anything much in the documentation on this. ... View more

Hi This thread might interest you if you are on a Windows platform: SAS-wsm is available for use with SAS 9.4 deployments - SAS Support Communities @AndyForeman created a Powershell utility to work in a similar way to the Unix/Linux sas.servers script. It works to ensure that services start in the right order, and waits for the ones which take a while to come up completely (eg. the web apps). I adapted Andy's script to work in a multi-platform environment. There's a zipped version of that as an attachment to one of my posts in the thread. ... View more