02-13-2018 04:13 AM
I am having problems with a user profile and I am unsure if it is one problem or two.
First, background (skip to go direct to the questions):
Steps already taken:
Both the user and we are using SAS EG 7.1 and we are using SAS Management Console 9.4
Has anyone come across a similar problem? Very grateful for any input!
I have attached screen grabs of error messages he gets when trying to access.
The error message when he tries to log in to the SASApp server:
Logging in with windows password:
Trying to open the SASApp server in the server tree in SAS EG:
02-13-2018 10:10 AM
You may want to raise a track with your local SAS Technical Support.
The description you have already has lots of information, you may want to add some logs (Metadata Server, Object Spawner and Workspace Server).
The user can connect to the Metadata Server, it's already a good indication (it's not visible from the last screenshot but at the bottom right corner, you see the name of the user, right?).
And you are not using an internal account (such as user@saspw), correct?
Is the user part of the SAS group on the server? For instance, on a Windows environment it would grant him (usually) the log on as a batch job policy.
If you want to retrieve your Unrestricted account, please have a look at Unlock an Internal Account.
Hope that helps.
02-16-2018 03:47 AM
Thank you, Damo!
I followed your advice and contacted SAS Support, as we were unable to figure this out for ourselves. In case anyone is searching for the same issue, I will add the information from the support below and the step that helped us.
So, apparently, when a user tries to log on with credentials that aren't yet in the system SAS EG puts their credentials in "jail". Since the user rightly believed himself to be in the system, due to my botched profile, he tried to log on and his credentials got locked up.
Then, when he had a proper profile his, now correct and functioning, credentials were recognised by SAS EG - but as an "uninvited" user.
The solution for us was to refresh the Object Spawner. I have included the Guide link that support provided, to the section explaining how to do this: