About cj_blake

josevalenzuela

Finally the problem was solved with the help of @cj_blake . Postgresql ran out of space and he has increased it. Thanks!

jan_ehlers

Hi @JGon If you want to read or write files from SAS Content Folders I suggest you use the FILENAME FILESRVC statement: Accessing SAS Content with FILENAME FILESRVC in SAS Viya - SAS Support Communities Content Folders are best for smaller data files. If you have larger data files I suggest you create a DNFS caslib pointed to an NFS path and restrict permissions on the caslib to specific groups or users. From SAS Studio you can use a libname statement to process data in caslibs. For details on creating a caslib see this: SAS Help Center: Working with Data in CAS

cj_blake · ‎07-08-2025

Alright. It might be that you need to update your LD_LIBRARY_PATH environment variable to point to the location of those client file that you loaded. See here.

cj_blake · ‎07-01-2025

There isn't, actually. However, here are some steps to get you started. You should be able to access the ESM application by going to https://mypaygdomain.location.cloudapp.azure.com/esm/ . You'll be asked for login details and you can use: Username: esmadm Password: Same as your viya_admin user Once you're in you'll want to check out the Enterprise Session Monitor User's Guide for some information about the application. But, in addition that here's a few tips to get you started: The main menu is on the left - from here you can navigate around the application from the live view through the different historic searches If you want to see the sessions on your system right now, you'll want to check out the Live View If you want to see what users have been doing in their sessions you'll want to look into the "Events and Logs" section, select a time window and either select CAS Actions, or SAS Code Steps. Hope that helps!

cj_blake · ‎06-03-2025

@Maryam31 it might be worth making sure that your account satisfies all of the requirements in Microsoft's purchase validation checks.

cj_blake · ‎05-16-2025

@kollajagadeesh you're right, the current set of allowed actions do not include Microsoft.Network/networkSecurityGroups/join/action which is required to do what you're looking to do. I am going to check with a couple of colleagues what we think the best course of action should be.

Conor_H · ‎05-07-2025

You can now define tags at deployment time. Please share if this is the feature you were looking for!

DQM · ‎04-28-2025

How about East US?

cj_blake · ‎04-07-2025

@sanketkalyankar - did you manage to resolve this?

cj_blake · ‎04-07-2025

@klm-123 did the responses from @priyhat_sas help?

paul-blu · ‎12-09-2024

Can you explain how to do these manually? I have no clue how to initiate a restart, start/stop, or change a whitelisted IP address. I cannot find it in your documentation either.

cj_blake · ‎12-02-2024

@gordononline, I'm sorry to hear that you've been having so many issues with your deployments. We resolved an issue at the end of last week that I think may have been affecting many if not all deployments from early November. It's possible that your attempts may have been included in that. If you clear out those old deployments and attempt a new one in a known good region (say, US West), and try again, what do you get? If the deployment fails, and hopefully it doesn't, can you open the details of the error and send them over?

DQM · ‎10-10-2024

Hi, I currently have a workaround to resolve the unsecure connection warning by importing self-signed CA certificate. I followed the instruction provided below. https://go.documentation.sas.com/doc/en/viyaakscdc/v_001/viyaakstasks/n1ecr6sfxugizan1fte2gtme0ro8.htm

DQM · ‎10-10-2024

Hi, I have identified and resolved the connection issue. The root cause was the presence of multiple IPv4 addresses: one IP from my VPN and another as my original source IP. To gain access to the Jumpbox, I needed to add my source IPv4 address to the authorized IP range. (In contrast, I access the the deployed SAS Viya via the IPv4 from my VPN) I discovered my source IPv4 address while connecting to another Jumpbox without authorized IP ranges. The connection log displayed my IPv4 address when accessing the Jumpbox. Additionally, the source IPv4 address can be found on ifconfig.me. The first IPv4 address listed in the “X-Forwarded-For” row (highlighted in red) is the one recognized by the Jumpbox/Azure VM.

DQM · ‎09-27-2024

Just FYI, I deployed SAS Viya again today with defined IP ranges. It only took me 47 minutes 43 seconds. I guess the deployment time may depend on how fast Azure can execute the deployment script.

Online Status	Offline
Date Last Visited	Tuesday