About JuanS_OCS

JuanS_OCS · ‎03-08-2021

Hello @sunzhuofan , we will be happy to give you a hand, please share more information with us upfront as the current description is not enough: The screenshot of the error, the reference error text, the log file referenced by the error, your OS/version, your SAS version and maintenance, your SAS solution/product(s), etc etc. Thank you for understanding. Best regards, Juan

JuanS_OCS · ‎03-08-2021

Hello @sergie89 , good question. You can start by checking by yourself the Guide for Updates and the What's new section for the maintenances and per product.

JuanS_OCS · ‎03-01-2021

Hi @MariaD, Did you have a chance to look at the logs? If you have run SDM to remove configuration components, are more than one version of SAS studio listed? If so, I recommend to remove any older version, as they shouldn’t, but can potentially conflict with each other. Regards, Juan

JuanS_OCS · ‎02-10-2021

Wonderful compilation Simonm, @SimonMcGrother really useful as not everyone is aware of these documentation sites. Thank you! Aside from this, do you know if are there going to be specifics per Cloud environment? Is there a page on any of these two sites with information about the GIT repositories for Azure?

JuanS_OCS · ‎02-10-2021

Hi @sathya66 , a few questions, as it might be relevant information: what version of LSF/PM do you have? what Operating System? Is this LSF/PM on a single server, or on multiple Grid nodes? What is the underlying storage for this location? Local? Shared Storage? To me it seems as if either the process or file are locked or not accessible, indeed. In any case, the real reason or problem, you will find it into the logs of the process manager and the disk journal, comparing timestamps and aligning historic events and log messages. have you got the chance to do this?

JuanS_OCS · ‎02-10-2021

Hi @HangLui , it is possible. This is just a report: you can always copy it and modify the copy (never modify the original), to adjust the filters. Or to create your own report from scratch, I assume starting from one that is half-way done for your requirements it is a faster method. What I don't know is the retention time of the data in your environment, but you can always adjust that as well. So, in short, yes, all is possible

JuanS_OCS · ‎02-10-2021

Hi @LoriGoldman , just to complete on @ChrisHemedinger and @SASKiwi last responses: I cannot say if there will be more maintenances of SAS 9.4 (probably some more yes), but I can say that after SAS 9 SAS Institute has put out there SAS Viya, which is healthy moving forward and growing. The current version for on-premises is SAS Viya 3.5, and the last version is SAS Viya 4, which currently is supported only for the Microsoft Azure cloud. In short, there is SAS for a long while, as @ChrisHemedinger indicated. I hope this helps. Best regards, Juan

JuanS_OCS · ‎02-10-2021

Hi @HangLui , if you are an administrator, you should have access to the SAS Environment Manager and the Administration reports (normally shown as well in your Home page, at the bottom). One of the reports will give you the required information. https://documentation.sas.com/api/docsets/calmonitoring/3.5/content/calmonitoring.pdf?locale=en Nonetheless, you can always have a resource monitor or agent installed in any of your servers, and monitor them as any IT team would. I hope this helps. Best regards, Juan

JuanS_OCS · ‎01-28-2021

Hi @Samrat07 , this message is telling you that your Metadata server is having trouble connecting to one or more of your Object Spawners on one or more SAS compute server. You might resolve your must immediate issue by fully stopping all your Object Spawners and starting them again. All your sessions, including Studio and EG might go down. To fully resolve the issue, after doing this, you might need to check your Object Spawner logs and find the culprit of the issue. If you cannot find it yourself, I would recommend to contact SAS Technical Support and share with them all your logs and relevant information. I hope this helps. Best regards, Juan

JuanS_OCS · ‎01-26-2021

Fantastic! By the way, as closing remark, I liked very much the structure of your post, kudos to you for the effort.

JuanS_OCS · ‎01-26-2021

Hello @PriitL , there are a few things that I would recommend: 1- have a proper entry in the hosts file, aligned with how your original server was created (FQDN, shortname, aliases, etc) and pointing them to the IP of the new server. 2- Ensure the new server is in similar subnet as the original, otherwise multicast addresses must be updated. 3- Stop all services and clean up the work/logs/temp files from each service (let me stress it, each service). 4- Start all services and validate the system 5- If it works, you should think about the change hostnames and rest of actions, in order to remove the temporary entry in the hosts file. Still, this clone probably won't be ready to be a real production system, as this procedure is not officially supported by SAS Technical Support, and I can tell you that chances are high you might have challenges during the life cycle of this clone. If you use, you will assume all the risks. Furthermore, this clone does need a new license you need to purchase at SAS Institute. Otherwise, legally speaking you would be incurring in one of the contract termination clauses defined in your supplement. Unless, of course, this clone is something discussed and agreed with your SAS Account Manager. I hope it helps. Best regards, Juan

JuanS_OCS · ‎01-26-2021

Thank you for the share @SriLaxman , I like the simplicity of the script. I adhere to @sandeeppajni2 recommendation. I would always recommend to implement High Availability, an approach supported by SAS Technical Support, and would give you an approach with some additional nice features for the user and the administrator. Is there any particular reason why HA is not implemented in your SAS Grid Manager platform?

JuanS_OCS · ‎01-26-2021

Thank you for the update Tom / @thomasm516 and very glad to know your issue was resolved. You can go ahead and mark your last post as the solution to your topic, I am sure it will help some folks in the future.

JuanS_OCS · ‎01-26-2021

Thank you very much @ashasupriya, it is a very appreciated tip, I am sure it can help many. Not only for this particular issue with Remote Services, also for many others that are related to the Java Picklist class, as most of the components in SAS 9 are built in Java code. Aside from this, @ashasupriya, does your SAS Tech Support representative know how this happened and if it will be resolved with a hotfix, in a SAS note or in a new version of SAS Depot?

JuanS_OCS · ‎01-26-2021

Hello @SAS_LuisBolivar , in addition to the indication by @AnandVyas , I would check if your license has been properly updated, in your SAS binaries and in your SAS Metadata. This kind of message is relatively common in these case, strange behavior can be found. https://blogs.sas.com/content/sgf/2016/08/02/two-steps-to-update-your-sas-license-and-check-if-it-is-updated/ http://support.sas.com/kb/49/750.html http://support.sas.com/documentation/installcenter/en/ikunixplannedri/66610/PDF/default/setinit_planned.pdf Please let us know how it goes, I hope this helps. Best regards, Juan

Online Status	Offline
Date Last Visited	‎04-13-2026 07:47 AM