About AjmalFarzam

AjmalFarzam · ‎12-13-2018

Hi, Is the Remote Procedure Call service started on your machine? Also make sure the Print Spooler service is started.

AjmalFarzam · ‎12-11-2018

Hi @MariaD, http://support.sas.com/documentation/cdl/en/appsrvtuning/69859/HTML/default/viewer.htm#n0xfno04p3q3urn1513f8zdjx72m.htm lists the minimum limits for the web/middle tier on Linux. The nofiles value is for open files.

AjmalFarzam · ‎12-10-2018

Hi, Only the ODBC SQL Driver is required, and the SQL client is not necessary. The error message suggests a problem with the secure connection. Do you have the right connection information? Double-check the port number in particular.

AjmalFarzam · ‎12-10-2018

Hi, When you say your office disabled TLS 1.0, do you mean they disabled TLS entirely or just restricted the TLS protocols (e.g. to TLS 1.2). If the latter, make sure that Local Security Policy > Local Policies > Security Options > ‘System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing' is set to enabled. I think you'll also need to reboot. Also, have a look at the Control Panel > Administrative Tools > ODBC Data sources. Look for the data source with the name you have specified in your libname with the DATASOURCE= parameter. Look at the properties and verify that all parameters are correct, paying particular attention to the port number. You can Test Connection from here to see if it is accessible.

AjmalFarzam · ‎12-09-2018

Hi, I think the 'Reverse Lineage' option in BI Lineage Plug-In is what you're after: https://go.documentation.sas.com/?docsetId=bisag&docsetTarget=p14w0edwch53wdn1fior9hlxo39x.htm&docsetVersion=9.4&locale=en

AjmalFarzam · ‎12-08-2018

Is the WIP Data Server (and all other services) running?

AjmalFarzam · ‎12-08-2018

Hi, Can you validate the other servers successfully? I expect this is something to do with the changes made to enable logging, so I would double check those settings as @anja suggests. Can you run "WorkspaceServer.bat -dms"? Does it launch successfully? Do you see any errors in the Object Spawner log?

AjmalFarzam · ‎12-06-2018

Sorry I deleted my last post as it wasn't quite accurate. You mentioned this is occurring for programmers using EG and in batch. Do you have MYSASFILES set in another sasv9.cfg file elsewhere? For example, check the following: E:\Program Files\SASconfig\Lev1\SASApp94\sasv9_usermods.cfg E:\Program Files\SASconfig\Lev1\SASApp94\WorkspaceServer\sasv9.cfg E:\Program Files\SASconfig\Lev1\SASApp94\WorkspaceServer\sasv9_usermods.cfg E:\Program Files\SASconfig\Lev1\SASApp94\BatchServer\sasv9.cfg E:\Program Files\SASconfig\Lev1\SASApp94\BatchServer\sasv9_usermods.cfg Check this post for more info on the sequence in which the config files are processed: https://communities.sas.com/t5/Administration-and-Deployment/SAS-Config-Files-Sequence/td-p/375889

AjmalFarzam · ‎12-06-2018

Hi, Which SASApp server is returning the error? Have you checked the object spawner logs?

AjmalFarzam · ‎12-06-2018

Hi, Any clues in the hq-server.log file? What steps did you perform to disable TLS?

AjmalFarzam · ‎12-06-2018

Hi, In which location on the server did you see those config options set? They may be being overridden by a setting elsewhere. What are the 'programming folders' you are referring to?

AjmalFarzam · ‎12-04-2018

Hi, I would suggest raising this one with SAS Technical Support. Those WARN messages do not necessarily indicate a problem with those components, but just that they are waiting for something. Do all other services in the environment start OK? Are all the other logs free of errors?

AjmalFarzam · ‎11-29-2018

What version of SAS are you on? You may need to review the mail server settings Environment Manager is using (they can be different to the email system params you use in a Base SAS program). See http://support.sas.com/documentation/cdl/en/evug/69029/HTML/default/viewer.htm#p18n3hxpsz255zn1432pf2s42cv3.htm

AjmalFarzam · ‎10-25-2018

Hi, Are you sure the first job is finishing with the right exit code? Does it turn blue in Flow Manager? As Christian suggests, you might need to uncomment the last 5 lines of sasbatch.sh to allow SAS jobs that complete with warnings to return an exit code of zero. Some more info on this can be found at https://support.sas.com/rnd/scalability/grid/platformfaq.html

AjmalFarzam · ‎10-24-2018

If you right click on the job in Flow Manager, you should see an option to view runtime attributes, which should include the log file for that particular job. Typically it should be under <config>\Lev1\SASApp\BatchServer\Logs (depending on how your environment is configured).

Online Status	Offline
Date Last Visited	‎11-07-2024 10:31 PM