Hi, I'm facing some similar issues, but  I've upgraded from M6 to M8, Could be please let me know if the issue you've faced is resolved and steps taken to resolve this. ... View more

Yes, SCCM (and, in the future, Intune) is worth it for us as we have upwards of 300 users. But even with admin rights downloading hotfixes directly won't work because of firewall/proxy policies which prevent the download of executables (we have an extremely risk-averse Cyber Security Branch). We have to use a "staging server" in our extranet and then pull them directly from that to a location on our corporate network. And we don't upgrade the clients unless we are doing so to our main platforms, and so get a new software depot. ... View more

Thank you @Eddie305 that's what I needed! I'd been looking at this section: SAS Help Center: SAS Migration Utility Reference ... View more

Your shell doesn't appear to be running with elevated privileges. Try right-clicking the .exe and choose Run as Administrator. ... View more

@ecruz1989 I wouldn't have liked to attempt it on our own as it was far from straightforward, so we contracted SAS to do the upgrade. I can't remember the overall number of hours they quoted was, but the actual technical work was considerably less than 160 hours even accounting for the complications we encountered. We were responsible for backups, which was reasonable. In our case this was taking snapshots as the servers are VMs.  ... View more

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 see this in your gemfire log [severe 2025/05/26 10:33:15.036 IST <main> tid=0x1] Could not bind locator to null[41,416] This means that the port 41416 is busy. Do you have any other instance of SAS running?  You can perform the following 1. Make sure port 41416 is not being used by any other process.  2.If it is not, then stop SAS , stop the machine 3.Restart the machine and start SAS See it works or not. ... View more

In order to use OAuth options, while configuring the ODBC manager select the Authentication Mechanism as OAuth2. The next step would be to fill the necessary Oauth2,HTTP and SSL  options as applicable at your place and you should be good. No authentication statement would be needed in the libname statement. ... View more

Hi Dr. Abhijeet, To set SAS 9.4 as the default, try this: Right-click on a .sas file → Open with → Choose another app → Select SAS 9.4 → Check the box "Always use this app to open .sas files" → Click OK. If SAS 9.4 doesn’t show up, click "Browse" and manually select the SAS executable (usually in C:\Program Files\SASHome\SASFoundation\9.4\sas.exe ). ... View more

If you check @Nigel_Pain 's link then you will see that only Intel / AMD-style x86 processor architectures are supported not ARM. ... View more

There is no OOTB options for generating lists. Job Monitoring might here as well, I haven't tried it. The deployed/scheduled (active) job flows are visible within SMC and crontab. The executed job flows are logged in your configuration directory. These logs are usually easy to grasp, but they still are not lists. This information could probably be extracted from metadata, but that's outside what I have don in the past. ... 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

In a manual migration, when you import the metadata package (.spk file), you get a choice as to whether you want to include/import access controls or not. The access controls are always exported in the spk file but you get to choose whether you want to import them or not.   Although there may not be any manually added access controls on the content in your user folders there will be some access controls added automatically by SAS when the user folder was created. You will see an ACT (Private User Folder ACT) and a set of explicit permissions on each users "My Folder" and "Application Data" folders.  This sample screenshot of the Metacoda Permissions Tracer shows them and their impact on a users My Folder:     It is these automatically added access controls which prevent users from seeing inside each others user folders but allows them to add content to their own. You will most likely want to retain that setup in the new environment by importing the access controls. Alternatively if you get each user to login into the new environment so that SAS automatically creates and secures the user folders then you can import the user folder contents later without access controls and let permission inheritance do its work.   Thanks @Nigel_Pain for mentioning our plug-ins. As mentioned, you might find these useful to review and/or test the metadata security implementation in your old and new environments. If you want to try them out you can register to get a free 30 day evaluation license at https://www.metacoda.com/en/evaluation/ ... 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

@Madelyn_SAS , Thank you for quick help. ... View more