When starting the Direct Agent, the following error might occur in the onprem-direct.log file before the agent attempts to start:
2023-04-17 09:38:06,096 ERROR [pool-18-thread-12] SID[] USER[] CC[] [] ics.crm.security.ejb.SecurityManagerBean - Problem logging in
com.sas.svcs.cluster.httpinvoker.UnavailableServiceException: The system attempted to find and access a service for interface 'org.springframework.security.core.userdetails.UserDetailsService' for 2 hours and was unsuccessful.
The SAS services not being started in the correct order is the main cause of this error. For additional information, see Starting Servers in the Correct Order.
Note: For the Windows environment, make sure that you are running the Direct Agent as a service. For additional information, see Running the Direct Agent as a Service in Windows.
Workaround
To resolve this error, complete the following steps, which are specific to your setup:
- Stop the Direct Agent under services (default “CustomerIntelligence360Satellite” service name).
- Stop all SAS services.
If you stop the servers using the list that is provided in Starting Servers in the Correct Order, make sure that you stop the services in the inverse order from the chart. SAS® Web Infrastructure Platform Data Server and SAS® Metadata Server should be stopped last.
- Make sure that there are no SAS processes still running. You can check if there are SAS processes running under the Windows Task Manager. (For example, make sure there are no sas.exe processes still running.)
- From the Windows Task Manager, select the Command Line column in order to see the command that was used to launch the processes.
- Look for processes that are running under the sassrv user account and for sas.exe processes that are running and end them.
- Start all the SAS services in the proper order. See Starting Servers in the Correct Order for additional information.
- Wait 30 minutes to give the SAS web applications plenty of time to start up. After 30 minutes, start the Direct Agent (which contains the default “CustomerIntelligence360Satellite” service name).
- Make note of any error that you might encounter. If the same errors occur immediately, validate . Details about how to validate SAS Platform are in the Instructions.html files located in the <sasconfig>/Lev1/Documents/Instructions.html or <sasconfig>/Lev1/Documents/Backups folders
An example of the validation steps,
In SAS® Management Console, validate the following:
- the SAS® Content Server
- the SAS Pooled Workspace Server
Then, validate the following in the mid-tier:
- Ensure that the starts.
- Make sure that you can log on to a web application (such as SAS® Studio or SASAdmin).
- Validate the clients.
- Make sure that you can log on to SAS® Information Map Studio and/or SAS® Enterprise Guide® .
Note: If you restart the server to restart the services, change the Direct Agent to start manually (default “CustomerIntelligence360Satellite” service name) before restarting the servers. Then, restart the Direct Agent service manually after 30 minutes to give the SAS web application services a chance to start up properly.
