Hi,
when i right click the SASApp - Workspace Server, it is asking for user name and password . In my password list there is specific password used for ObjectsSpawner ID. when i use that i geeting an error . in the services also i should change local to ObjectsSpawner account.
To be able to logon remotely the account would need the permission to RDP to that server.
Hi @senu188
To validate a workspace server you can use any account that is configured to use SAS i.e. account should exist on local server or AD if PAM is enabled, should be in SAS Management console and with a home directory.
While I don't understand fully your question regarding changing object spawner account, usually object spawner service is started using the SAS installer account and workspace is validated using any valid SAS account as stated above, ex: sasdemo.
Hi,
i validated worksapce server with sassrv account . Iam trying to change the olap server to neoobspsvc2 ,it is popuping to restart the services, but when i tried to restrat it is not accepting . any other way to change or what action to take?
Is the user ID and password correct? Is the user part of "Logon as Batch Job" group?
Hi,
Yes user name and password is corrrect. When i enter it is accepted,when i restart the services to make effective ,it is saying password wrong.the user is addded in "Logon as Batch Job", but no luck .
You can check the Windows Event Viewer to see if there is any additional information. Note you may need to grant additional privileges for an account to be able to run a service.
Note: In most cases, an object spawner on Windows runs as a service under the local system account. If the spawner instead runs under some other account, that account must be a Windows administrator on the spawner's host and have the Windows user rights Adjust memory quotas for a process, Replace a process level token, and Act as part of the Operating System. These user rights assignments are part of the local security policy for the Windows computer that hosts the spawner.
Source: SAS 9.4 Administration - Windows Privileges
Using something other than Local System is optional so this is a choice you are making.
If I had to guess why, I would say it may be so your OLAP Server can access data on a shared file system that the Local System account does not have permission to access, or that your security policy requires it.
If everything works with local system, the issue must be with what you are entering. Either the user/pass is entered incorrectly or the host otherwise cannot validate that user/pass seems to be what typically produces that message. Are you able to log in to that host with that user/password combination?
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.