in the new SASM8 environment we have been receiving the below error when user submits the job with SASGSUB and GridServer Logs complains the below error . when I submit the sample job with my id (not SAS installer) job is successful but user jobs are reporting 105 errors in the "bhist -l" output with below error in /Lev1/SASApp/GridServer/Logs. I switched to the user and checked he is able to access all relevant config and log locations and have write permissions as well. Is there any other permissions I need to set on OS level OR any fix is available for this?   ERROR: Invalid option value /sas/foundation/config/Lev1/SASApp/GridServer/logconfig.batch.xml for SAS option LOGCONFIGLOC. ERROR: (SASXKRIN): KERNEL RESOURCE INITIALIZATION FAILED. ERROR: Unable to initialize the SAS kernel.     ... View more

I have 100's of SAS Flows which I have done a manual metadata export and import including Jobs and Deployed jobs. Everything has been migrated successfully BUT only few flows came over to the new environment with the previously scheduled(in old environment) options, I mean no clock symbol on the flows in the new environment. while others are migrated with out a schedule [No clock symbol on them]   1. Is there any options I need to consider to get all flows as-is (including schedule) 2. How to migrate LSF schedule files from /lsf/pm/work/storage/flow_storage? - I know when I manually schedule the flow these files will be created, but I have 100's of users and all the flows has been scheduled by them and we dont want to ask everyone to do this for every flow in new envi. 3. If I move lsf flow files to new environment and Metadata flows (with or without schedule, clock symbol) will these flows start as per the schedule?. ... View more

I am performing a manual metadata migration from M6 to M8. In the old environment users created metadata objects on own metadata user folders with their own user id , no folder structure followed on BU/ORG level and no ACT's applied.    I am performing migration with the account "sasadm@saspw" and would like to ensure users will not have permission issues on their folder/objects after moving to the new environment(sasadm vs Individual user-id).    ... View more

I have a new M8 setup and we are connecting to SQL server using Access engine through provided Datadirect drivers    LIBNAME SQLSRVT SQLSVR Datasrc=MyDatasrc SCHEMA=MySchema authdomain="SQLSRV"; Authentication is successful but it does not list Schema tables in the library   I have some users connecting to SQL server using long Libname definitions: LIBNAME SQLSRVT1  SQLSVR NOPROMPT="Driver=SAS Institute, Inc 8.2 SQL Server Wire Protocol; AuthenticationMethod=9; Database=MYDB ; HostName= MyHost\SSINST; PortNumber=Myport; Domain=MYDOMAIN; LogonID=[username]; Password=[password];" Schema=MySchema;   Library assignment is successful and it list tables. Can you suggest where this is going wrong?   Below are the ODBC.ini entries for libname using AuthDomain   [DataSRC] Driver=/sashome/AccessClients/9.4/SQLServer/lib/S0sqls28.so Description=SAS Institute, Inc 8.2 SQL Server Wire Protocol AuthenticationMethod=9 Database=MyDB HostName=MyHost\SSINST PortNumber=MYPORT EncryptionMethod=6 ValidateServerCertificate=0 Trusted_Connection=Yes QuotedId=yes IntegratedSecurity=false TrustServerCertificate=yes CryptoProtocolVersion=TLSv1.2, TLSv1.1,TLSv1, SSLv3, SSLv2 SSLLibName=/usr/lib64/libssl.so.1.1 CryptoLibName=/usr/lib64/libcrypto.so.1.1   ... View more

Hello,   Is there any option to bulk update the command lines for all deployed metadata jobs ? we have a change in file paths as below and all our metadata deployed jobs have the command line referencing to old one, I dont have an option to update it dynamically during the metadata migration. OLD : /opt/sas/sasconfig_node/Lev1/../../.. New : /opt/sas/config/Lev1/../../..   All .sas files migration has been taken care on unix level. ... View more