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

[marceloctorres]

Hello!

I did what you suggested and these are the results:

Additionally, these are the contents of the file arcgis-monitor-agent-service.wrapper.log:

[StevenBeothy]

Hi Marcelo
Because the nslookup command failed, if you can try having your IT group create a Reverse DNS Lookup Zone and PTR Records for each of your servers. See if this fixes your problem.

You can test with the nslookup command and see if a PTR Record does not exists for your servers.

[marceloctorres]

Hi Steven

These are the results:

[StevenBeothy]

Hi Marcelo 

That IP does have a PTR record, is 10.0.0.4 the IP Address of the machine with the agent installed that does not have its config-store directory created?  

You can run "ipconfig" in cmd prompt to confirm the ip address you can enter in the "nslookup" command.

For security purposes, don't include your FQDN's and ip addresses in the screenshots of this public forum.

Are you using a gMSA for your Monitor Agents?

[marceloctorres]

Hi Steven!

Yes, 10.0.0.4 is the ip of the machine with the monitor-agent instaled:

[DerekLaw]

All,

In ArcGIS Monitor 2025, we’ve identified a regression in the DNS lookup logic run in AM Server and AM Agent when they boot up. We’ve seen this manifest in certain environments with no DNS available or under certain DNS lookup/name resolution configurations.

We understand this is a critical issue and we are working on a fix to address this issue ASAP.

------------------------

@JeffGarcia - I realize you're using a different Monitor release, can you please try some of the suggestions posted by @StevenBeothy to help resolve your issue?

[DerekLaw]

UPDATE: 

The Monitor Dev team just finished work on the patch for BUG-000177693. It is now in final test certification and we expect it to be available by mid to late August.

The underlying cause is related to DNS resolution (e.g., nslookup command) on the network, which is assessed when the ArcGIS Monitor software loads. This can be an issue for network environments without DNS or, in some unique network configurations where these DNS resolution commands fail.

We apologize for the inconvenience and thank you for your patience.

Hope this helps,

[DerekLaw]

UPDATE 2:

I've been informed by the release team that the ArcGIS Monitor 2025.0.1 patch was just published on MyEsri and is available for download now.

Hope this helps,

[ErikLash4]

Test on my dev env which is in a canned domain config (nothing special/unique) - first agent registration attempt after registering the servers agent. Error saying that the agent is already registered.

This is a clean monitor server installation, new VM, patched installer from this week. The target vm has never been registered with it before and is not showing up as a registered host on the server.

Haven't tested any workarounds yet but so far not off to a great start.

Edit -

Found issue to be that  "C:\Users\[ArcGISMonitorServiceAccount]\AppData\Local\ESRI\ArcGISMonitor\config-store-client"  from the previously installed version of the software was left as a remnant after uninstallation and no longer editable? by the ESRI installer. 

Workaround was to craft a PowerShell script to delete that folder from all of my servers prior to installing the new agent software.

New agent installed on all of my production VMs including the ones in the DMZ. Note that it registered the DMZ machines by their IP instead of name, which is fine by me.

[CalvinHarmin]

I'm not sure if my issue is exactly matching others in this thread but I figure I ought to see if anyone has any pointers. I have a Windows Server 2019 VM with ArcMonitor Server and just upgraded 2025.0.1 and upgraded all of my Agents.

My federated Arc* machines are Portal, Server (my main/hosting server), Datastore, GeoEvent Server. I also have a postgres server and Cityworks server that I monitor.

All of my these machines have no trouble registering with Monitor except for my (hosting) Server machine. I have had 2023.x and 2024.x previously, and even tried a Linux VM instead of Windows hosting Monitor Server in the beginning. In all cases, all my machines register exactly as they are supossed to, but my Server machine cannot register with Monitor server. The registration makes the initial authentication call [success]! ... but then nothing else happens. Monitor site logs also record the two entries for the authentication call from my Server machine's IP (message 'API request started', 'API request ended'), but nothing else related to the registration event is logged (debug level enabled).

I had a months-long ESRI ticket that went nowhere. We went so far as to use wireshark and log the traffic happening -- it seems the connection is simply closed after the initial authentication call, with no other logs or indication of what is happening to cause the connection to close, whether it's being aborted by the Server or the Agent side. We have disabled anti-virus on both the Server and Monitor machines to test if that had any effect (nope), we've updated all of our machines with CA SSL certs for the backend communication just in case that had any effect (nope).

I've carefully followed every step in the documention to ensure the domain account running the ArcGIS Monitor Agent service has access to the bin, framework, and appdata config-store-agent directories. This account is also a local Administrator account, and it's in the Perfomance Monitoring Group.

Mind you -- no additional actions like this whatsoever were required when registering the Agents with Monitor on my other machines, which are all essentially the exact same in terms of VM/Windows base image, domain accounts as local admin, networking, etc.

Does anyone have *any* potential clue what might (not) be happening here?