In that case you can start by looking at the authorization of the batch user on the pre-assigned libraries. The batch user should atleast have ReadMetadata permission. Also, which engine are you using as the pre-assignment type?
You should make sure that the appropriate server is selected inside properties of those pre-assigned libraries so that it can retrieve the library definitions from metadata. Also, you should edit SAS-configuration-directory\Lev1\SASApp\BatchServer\sasv9_usermods.cfg and add the below option -metaautoresources 'SASApp' Check out this documentation for more details https://documentation.sas.com/doc/en/bicdc/9.4/bidsag/p0u8xcdo2ll3kmn1oqfz2s0ybooq.htm#p17nlo3gas3kk...
This update was already done and also for your reference, I could see in the log, that when I run the job with any other user in the batch mode, the libraries are pre assigned , but when I run the job using batch user , I get this message in the log:
NOTE: No preassigned object definitions were found on the metadata server.
In that case you can start by looking at the authorization of the batch user on the pre-assigned libraries. The batch user should atleast have ReadMetadata permission. Also, which engine are you using as the pre-assignment type?
Indeed was something to do with permissions. Thank you @sangavis37
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.