topic Re: No preassigned object definitions were found on the metadata server in Administration and Deployment

No preassigned object definitions were found on the metadata server

Mushy — Wed, 22 Feb 2023 08:46:21 GMT

Hello All,

When I run the SAS job in the batch mode, I get the following note, even though there are pre assigned libraries:

NOTE: No preassigned object definitions were found on the metadata server.

But when I login via EG, I see all the preassigned libraries.

Any help is appreciated!

Thanks

Mushy

Re: No preassigned object definitions were found on the metadata server

sangavis37 — Wed, 22 Feb 2023 10:21:57 GMT

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#p17nlo3gas3kkkn1acj5kkjhj1h7

Re: No preassigned object definitions were found on the metadata server

Mushy — Wed, 22 Feb 2023 11:02:22 GMT

@sangavis37 Thanks for the response .

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.

Thanks,

Mushy.

Re: No preassigned object definitions were found on the metadata server

sangavis37 — Wed, 22 Feb 2023 12:05:24 GMT

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?

Re: No preassigned object definitions were found on the metadata server

Mushy — Wed, 22 Feb 2023 12:36:13 GMT

Indeed was something to do with permissions. Thank you @sangavis37