Hello @Mahis  Please check if the user has access to the location defined for work library. ... View more

Please have a look at this https://communities.sas.com/t5/Developers/VBA-COM-quot-Class-not-registered-quot/td-p/716112 ... View more

Yes. Typically changes to metadata server are captured in the metadata server logs. ... 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

Hello @TimBedsted , @nstdt  Please have a look at the post by @ChrisHemedinger  at Re: Executing python code from SAS Environment - SAS Support Communities Please note that the value of MAS_M2PATH should represent the actual path of mas2py.py . Similarly, the value of MAS_PYPATH should be the actual path of python executable.  If you still have issue, you can try appending the path of python.exe and mas2py.py to the   system PATH variable (i.e., environment variable) OR add the following to the SAS EG options options SET=PATH=SYSGET(PATH):[path of python.exe];[path of mas2py.py]; ... View more

Hello Please have a look at this paper 008-2012: A Guide for Connecting Java to SAS® Data Sets ... View more

In case this issue is occurring only in the production environment, please work with your SAS Administrator and investigate the cause. Do look into the program and server logs. If possible, enable the workspace server log to capture the logs for this program. ... View more

Hello @sascode  To your question "Now I am wondering can this be achieved in SAS if am asked to shift from R to SAS programming?" the answer is simply speaking a big yes.    ... View more

Hello @freshstarter  From what that has been posted it is difficult to ppin point the cause. However, a small change in the format statement "format new_date date9," to " "format new_date ddmmyys10.;"   should solve your problem. This can be verified from the code below. option locale="EN_GB"; data test; format dt1 ddmmyys10.; dt1="12JAN2024"d.; run; proc export data=test outfile="/full_path/test.csv"; run; The csv file had the correct format "12/01/2024" irrespective of where you open it (notepad or Excel). I have verified with both 12th Jan and 31st Jan. It works as expected.     ... View more

Hello @f_coutinho  Please have a look at these references (and further reverences in these articles) https://communities.sas.com/t5/SAS-Communities-Library/How-to-Run-SAS-Programs-with-Parameters-in-Batch-in-SAS-Viya/ta-p/816578 https://communities.sas.com/t5/SAS-Communities-Library/How-to-Run-SAS-Programs-in-Batch-in-the-New-SAS-Viya/ta-p/732126 IMHO Sas Viya is a distinct application on its own with good level of functionality in Common with SAS  9.x. But it is not the  same as SAS 9.x. Let us not look for 1-1 match between features. ... View more