Unable to Register Monitor Agent

[JeffGarcia]

I have a multi-machine deployment and am attempting to register the monitor agent (2024.1.1) for the various enterprise (11.3) components. When attempting to register the agent, I am given the following error message: 
[ error ] Cannot access ArcGIS Monitor agent: CLI commands require the agent to be running.

I have confirmed the agent is up and running on my portal and server machines and am able to reach the monitor server endpoint 30443/arcgis via web browser. I have also modified my pg_hba.config file to include the proper IP addresses for the various machines in my network. Any suggestions or advice is greatly appreciated.

Thank you,

Jeffrey Garcia

[JeffGarcia]

Not sure if this is related since I was seeing a different error. We were able to resolve the issue I had originally posted about just yesterday with ESRI support. Our environment required us to set proxy environment variables for AWS CLI use which is what was blocking the monitor agent from registering with the monitor server. By adding the FQDN of the monitor server machine and localhost to the NO_PROXY variables this resolved the issue we had been encountering. May be worth checking on your end. Go to settings > advanced system settings > environment variables.

[Tim_White]

Had a very similar experience - and finally found the cause about an hour ago, which is that Powershell was missing from the PATH environment variable on that specific server (coincidentally our hosting server too). I believe the Agent attempts to take an inventory of the host it's running on prior to attempting the registration, and uses Powershell to do that.

Hope that helps!

[CalvinHarmin]

You hoped that helps! Omg… holy $&@!

I could kiss you. I want to buy you lunch. I praise your name and the names of your ancestors. Your little comment just solved a mystery that has plagued me for a year or more, and fruitless support cases that wasted literal days to weeks of my life.

I fully expected my server machine already had the path… but it didn't… my hopes began to rise…

I added the default powershell path

%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

And closed the env var menus, tried to register… it didn't work.

I logged out logged back in to Windows… didn't work.

Almost gave up then realized I should restart the Agent Service since it maybe runs that powershell inventory on startup… and that finally did the trick.

A thousand thanks!

[Tim_White]

On behalf of me and my ancestors, you're welcome!

[CalvinHarmin]

By the way, how in the world did you figure that out? I couldn’t find any documentation or logs to point to anything like that, where some expected Agent component or process/procedure was not running as expected. I was in total darkness.

[Tim_White]

I definitely didn't figure it out on my own. My support ticket went through the local distributor here in NZ, which was escalated to Esri. I was sent a copy of the Agent that had more verbose logging, which showed where things were stalling, then a comparison with processes running on a host that had registered successfully revealed PS not running on the problem host. It ran fine manually using the service account credentials, but when I first looked I saw the PSModulePath variable was correct. Took a second look today and found the difference in the PATH variable.

So very much a team effort - but I'll take the lunch if you ever make it down this way! 🙂

[ChrisSchofield]

Thanks @Tim_White this helped me massively too 🙂