Thank you @ChrisHemedinger. I fully agree with all your comments.
@ChrisNZ, actually, I do believe it is an admin question. I will explain below. But basically, if it is not related to code, to configuration of the SAS system (even if it is functional configuration), and I think this one could be one of those, I always recommend to bring it to the SASAdmins attention, especially if no one else is answering the question in the originally selected public.
@Krohn,
I think our focus should go to this message:
NOTE: Retrieving login information based on AuthenticationDomain from the SAS Metadata Server failed.
Your challenge here is to talk you your SAS Admin and ensure that, the account that actually runs the job and connects to the SAS metadata, can log in to the metadata and it is a user name.
I see often one of these cases (see in SAS Management Console or Active Directory):
the account is an account for a group. If this is the case, it is an account that cannot read metadata, per-se, because it cannot log in to metadata, it is used for outbound connections (to databases, to platform manager, etc)
The account is locked
The password set in SMC is outdated or mis-typed
The user account is not linked to the right group anymore
if you have a options statement to connect to the metadata, say, before or in the signon statement, you can always check if you could connect, actually, to the metadata with that account.
The easiest answer would be that, probably, someone has changed user/group definitions recently in SAS Management Console or Active Directory/LDAP. If those changes can be rolled back, the problem should be solved.
And if not, and cannot find the exact cause, perhaps you might need support from SAS Technical Support or even a SAS Consultant.
For the time being, please let us know how it goes, we will try to help.
... View more