A SAS Environment Manager agent might either fail to start or it starts and does not send data.

To resolve the problem when the agent does not start:

If the SAS Environment Manager agent fails to start, it generates the following error:

To solve this problem, follow these steps:

1. Stop the SAS Environment Manager agent. Make sure that all of the agent processes (for both wrapper and Java processes) are stopped.
2. Verify that the following TEMP directories exist on the target machine:
   • For the WX6 platform, verify that the %SystemRoot%\TEMP directory exists on the machine. If this directory exists, remove the agent.encrypt.lock file from the %SystemRoot%\TEMP\ directory.
   • For all other UNIX platforms, check the java.io.tmpdir Java environment variable for the location of \tmp directory. By default, the environment variable is set to either the \tmp directory or the \var\tmp directory. After you locate the \tmp directory, remove the agent.encrypt.lock file.
3. Start the SAS Environment Manager agent in the manner that you normally start it (or as instructed in the instructions.html file)

To resolve the problem when the SAS^® Environment Manager agent starts but does not send:

After all SASServer services start successfully in SAS^® 9.4, the SAS Environment Manager agent cannot connect to the SAS Environment Manager service even when the service starts successfully. When the connection fails, the following error is generated during SASServer start-up:

When this problem occurs, you can load the SAS Environment Manager application in a browser. However, you cannot see resources that are populated on the SAS Environment Manager dashboard because the SAS Environment Manager plug-in does not initialize successfully.

To solve this problem, follow these steps:

1. Stop the SAS Environment Manager agent by submitting the following at a command prompt:
   SAS-configuration-directory/Lev1/Web/SASEnvironmentManager/agent-5.0.0-EE/bin/hq-agent.ext stop

   In this case, ext represents the extension of the file based on your operating environment (Microsoft Windows: hq-agent.bat / UNIX: hq-agent.sh).

2. Delete the SAS-configuration-directory/Lev1/Web/SASEnvironmentManager/agent-5.0.0-EE/data directory or rename it to something similar to data_old.
   
   WARNING: Do NOT remove the SAS-configuration-directory/Lev1/Web/SASEnvironmentManager/server-5.0.0-EE/data directory, because this action will break SAS Environment Manager.
    
3. Delete the agent.encrypt.lock file from the system temporary directory, if one exists.
   • In Windows environments, the temporary directory is C:\Users\user-name\AppData\Local\Temp.
   • In UNIX environments, the temporary directory is /tmp.
4. Restart the SAS Environment agent by submitting this command at a prompt:
   SAS-configuration-directory/Lev1/Web/SASEnvironmentManager/agent-5.0.0-EE/bin hq-agent.ext start

   In this case, ext represents the extension of the file based on your operating environment (Windows: hq-agent.bat / UNIX: hq-agent.sh).

   Important: Under Windows, restart the agent from the Windows command prompt. Do not use the Windows service manager.

After you submit the command, you should receive the following output in the command window that shows that the task was successful:

If you open the Environment Manager at this point, you should see the resources populating correctly on the Environment Manager dashboard.