Starting and stopping the EV Agent service

[Nigel_Pain]

SAS 9.4M7 on Windows 2012R2

I just renewed the SSL certificate on our mid-tier server, and the Java keystores for the webapps and Environment Manager. When I restarted EV the agents weren't managing to communicate with the EV Server. TS advised a solution to this, which was to remove the agent data directory and start using the command line rather than Windows Service Manager as per KB52668:

config\Lev1\Web\SASEnvironmentManager\agent-5.8.0-EE\bin\hq-agent.bat start

This worked. There were various messages which appeared after the command was run:

wrapper  | Starting the SAS [config-Lev1] SAS Environment Manager Agent service...
wrapper  | Waiting to start...
wrapper  | SAS [config-Lev1] SAS Environment Manager Agent started.
[ Running agent setup ]
Should Agent communications to HQ be unidirectional [default=no]: yes
What is the HQ server IP address: server.domain
Should Agent communications to HQ always be secure [default=yes]: Yes
What is the HQ server SSL port [default=7443]: 7443
- Testing secure connection ... Success
What is your HQ login [default=hqadmin]: sasevs@saspw
What is your HQ password: **Not echoing value**
What is the agent IP address [default=***.***.***.***]: server.domain
- Received temporary auth token from agent
- Registering agent with HQ
- HQ gave us the following agent token
    1654862220270-8565811125738354432-5097207690335336169
- Informing agent of new HQ server
- Validating
- Successfully setup agent
- Agent using new transport, unidirectional=true, port=7443

So my question is, what's the difference between running the command line and stopping/starting with Service Manager? TS weren't able to say.

Thanks.

[gwootton]

Running from the command line lets you see that output to confirm communication to the EV server was successful or if not, surface any failures that occurred during agent setup.

[Nigel_Pain]

Thanks Greg. But when I ran from services it didn't work, whilst running from the command line it worked first time. I can only think that the actual command run in the Windows Service must be different?

[gwootton · Accepted solution]

The service runs:
C:\sas94\Config\Lev1\Web\SASEnvironmentManager\agent-5.8.0-EE\wrapper\sbin\wrapper-windows-x86-32.exe -s C:\sas94\Config\Lev1\Web\SASEnvironmentManager\agent-5.8.0-EE\conf\wrapper.conf

hq-agent.bat runs (when called with start):
:start
"%_WRAPPER_EXE%" -t %_WRAPPER_CONF% "%wrapper_update1%"
ping -3 XXX 127.0.0.1 >nul
call :setup-if-no-provider
goto :eof

The "setup-if-no-provider" bit runs the communication setup piece you see in the command line output (if it doesn't have a connection to the ev server set up already).