APM FSO Agent Troubleshooting KB

Prerequisites

Applications Manager user: you need an Admin user to generate the install command (Settings → Discovery & Data Collection → FSO Agent).
Target server privileges:
- Run the install command in an elevated PowerShell (Run as Administrator) on Windows.
- Run it as root (or with sudo) on Linux.
Required tools:
- The PowerShell execution policy must allow scripts.
- curl and wget must be installed on Linux servers.
Network:
- The target server must reach Applications Manager over HTTPS on the host and port shown under Agent Bundle & Capabilities → Applications Manager address.
- By default, this is the Applications Manager server agent port. If the server agent port is disabled, it’s the SSL port.
- If the target server needs a different address (for example an FQDN, IP address, or a NAT or proxy address), edit Host or Port there, save, and copy the regenerated install command.

How to read the output

The install command shows its progress in 5 steps:

[1/5] Checking administrator privileges / sudo access ... OK
[2/5] Checking existing installation .................... OK
[3/5] Connecting to <host>:<port> ....................... OK
[4/5] Downloading installer ............................. OK
[5/5] Installing FSO agent .............................. OK

If a step fails, it shows FAILED followed by an ERROR: message. Find that message in the table below.

Log file: if installation fails, fso_agent_register.log is kept in the folder where you ran the command. The device key is masked in this file, so it’s safe to share with Support. If the failure happens before Step 5 on Windows, no log file is created; use the message shown on screen.

Errors and fixes

Error shown	Cause	Fix
`Run this script from an elevated PowerShell (Run as Administrator).` or `No sudo access. Run 'sudo -v' to authenticate, then re-run this script.`	The install command was not run with administrator or root privileges.	Run the complete install command copied from the FSO Agent page: in PowerShell opened with Run as Administrator, or as root, or as a user allowed to use sudo. The command already includes `sudo`.
`ALREADY INSTALLED - nothing to do` or `Uninstall the existing FSO agent and reinstall? [y/N]`	An FSO Agent is already installed on this server.	No action is needed if the existing agent is working. To reinstall: Windows: uninstall the FSO Agent from Settings → Apps → Installed apps, then run the install command again. Linux: answer `y` at the prompt. If you see`Existing FSO agent kept - nothing to do.`, the answer was No, or the command ran without an interactive terminal (for example from an automation tool). Run it from a terminal and answer `y`, or first uninstall with `sudo /opt/applicationsmanager/monagent/bin/uninstall`.
`Cannot reach <host>:<port>. Check the host, port and firewall.`	The target server cannot connect to Applications Manager. Possible causes: the host name can’t be resolved from the target server, a firewall blocks the port, or the address in the command is wrong.	Test the connection from the target server: `Test-NetConnection <host> -Port <port>` (Windows) `timeout 5 bash -c "</dev/tcp/<host>/<port>" && echo open` (Linux) If the host name doesn’t resolve, change Host to an FQDN or IP address under Agent Bundle & Capabilities → Applications Manager address, then copy the new install command. Allow the port in any firewall between the two servers.
`Download failed …`	The installer couldn’t be downloaded. Possible causes: `wget` isn’t installed (Linux: `wget exit code 127`); the FSO Agent bundle on Applications Manager doesn’t include the installer for this OS; or a proxy, firewall or TLS setting is blocking the download.	If the message shows `wget exit code 127`, install wget (`yum install wget` or `apt-get install wget`) and retry. From the target server, try to download the installer: `https://<host>:<port>/resources/FSO/latest/server/windows/installer/ApplicationsManager_Windows_Installer.msi` `https://<host>:<port>/resources/FSO/latest/server/linux/installer/ApplicationsManagerFullStackAgent_LinuxIns.sh` If it returns 404 Not Found, upload the latest FSO Agent bundle in the FSO Agent Bundle step and retry. Otherwise, allow HTTPS downloads from Applications Manager on the target server and make sure TLS 1.2 is enabled.
`Installation failed (msiexec exit code <n>). See <log>` or `Installer finished, but no FSO agent was found at /opt/applicationsmanager/monagent/bin/monagent. See <log>`	The installation did not complete.	Open `fso_agent_register.log` and check: msiexec exit code 1603: search for `Return value 3` and check the lines just above it (often permissions or antivirus). 1618: another installation is in progress. Wait for it to finish, or restart the server, then retry. 1625: installation is blocked by system policy. Contact your system administrator. No FSO agent found: check the “Install” section of the log. Common causes: the target server couldn’t download the agent files from Applications Manager; the device key was rejected; or the server isn’t a 64-bit x86 server (check with `uname -m`).
`… cannot be loaded because running scripts is disabled on this system.`	The PowerShell execution policy blocks scripts.	In the same elevated PowerShell window, run `Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass` and run the install command again. If the policy is set by Group Policy, contact your system administrator.
`WARNING: Could not send '<stage>' status to AppManager …`	The install command couldn’t update its live status in Applications Manager.	You can ignore this; installation continues normally. If the FSO Agent page doesn’t show the correct status, generate a new install command next time.

Still need help?

Email appmanager-support@manageengine.com with:

the full console output of the install command
fso_agent_register.log, if it exists
<Applications Manager Home>/logs/agent/server_agent.txt and server_agent_err.txt
the target server’s OS and version, and your Applications Manager build number