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]

I'm experiencing the same issue with Monitor Agent 2025.0. I tried to check the Agent service logs at C:\Users\arcgis\AppData\Local\ESRI\ArcGISMonitor\config-store-agent\logs (where arcgis is the local account running the Monitor Agent service) and noticed  the folder C:\Users\arcgis\AppData\Local\ESRI does not exist. I uninstalled and reinstalled the software using different local accounts, but the behavior remains the same. I even manually created the folders, granted Full Control permissions to the local account, and also copied the folders and files from another working Agent service at other machine, but it still doesn't work. 

[StevenBeothy]

Hi Marcelo and Jeffrey 

Can you test and confirm if either of the two issues I came across with another client might also be the reason why you are having issues registering your 2025.0 ArcGIS Monitor Agent with the Monitor Server and report back?

Reverse DNS Lookup (PTR Record) Issue:

2025.0 ArcGIS Monitor Agents seem to now require machines to have a Reverse DNS Lookup (PTR Record).

This has been captured in the AGM forums by an end user.

From what I tested, what seems to be happening is without a PTR Record, the monitor agents don't create their config-store directories under their service accounts. After a PTR Record was created for these machines, the monitor agent successfully created its config-store, and would successfully register with the monitor server.

gMSA Issue:

Another similar issue found was with the 2025.0 ArcGIS Monitor Agents when trying to change the local service account to a gMSA.

The Monitor Server had no issues having its service account changed from a local account to a gMSA. The 2025.0 Monitor Agents on the other hand, once I changed its local account to a gMSA, again we didn't have their config-store directories created so for a temporary workaround, we left these to either a local account or domain service account.

[JeffGarcia]

Hi Steven,

I am using Monitor 2024.1.1 so I believe my issue is a bit different. The config-store directories were successfully created and do exist under the service account user. 

[StevenBeothy]

Hi Jeff, sorry I missed the 2024.1.1 detail.

Can you run the Debug Log Level command as noted by Lachlan ?
This command and other troubleshooting steps were well documented by Esri in the ArcGIS Monitor User Group #3: Troubleshooting Strategies webinar.

Does your ArcGIS Monitor Agent account have the correct permissions to the config-store directories? Can you confirm if an an Administrative Account was used to install the Monitor Agents? 

[JeffGarcia]

Steve,

I am not seeing any logs being captured in the file after enabling debug level logs. I have checked that permissions are allowed to the framework, bin, and config-store directories, and can confirm an admin account was used to install the Monitor Agents. 

Running the "arcgis-monitor-agent.exe --serve" command results in a warning error that states: "address already in use." However, I get the same results on my data store machine which was able to register the monitor agent successfully so I'm not sure this is truly the issue.

I also confirmed that the agent is "running/started" in the machine services and by using the "arcgis-monitor-agent-service.exe status." Somehow the agent CLI command is still unable to detect this.

[StevenBeothy]

Hi Jeff
Sorry it wasn't clear in the instructions but the commands below need to be ran from PowerShell and not cmd prompt for the "$env:LOG_LEVEL='debug'" command to work.

cd "C:\Program Files\ArcGIS\Monitor\Agent\bin"
$env:LOG_LEVEL='debug'
.\arcgis-monitor-agent.exe --serve

FYI I was able to reproduce a similar issue to yours by:

• Installed a new Monitor Agent 
• Revoking "config-store" permissions to the Agent Service account 

• Tried executing "admin:system:info" command and registering the Monitor Agent with Monitor Server (failed)

• Granted "config-store" permission to the Monitor Agent account 

• Successfully registered the Monitor Agent with Monitor Server

It might not be your exact issue but it's worth looking into if the Monitor Agent services has permissions to the config-store as noted earlier.

[JeffGarcia]

Thanks for providing those details steps Steven. I did a complete reinstall of Monitor Agent, switched to powershell, confirmed account permissions and the results are still the same. No error logs when attempting to register the agent or when executing "admin:system:info" command. I did notice that our domain account was not in the performance monitor user group so I added it in but that still did not change anything. I opened a support ticket for further assistance with this issue.

[marceloctorres]

Hello Steve!

I run ".\arcgis-monitor-agent.exe --serve" in a PS window, no errors, and run ".\arcgis-monitor-agent admin:system:info" in another window; these are the results.

Note that the config-store was created in the LocalAppData folder of the local account 'gisadmin', the local account with which the Windows session was started.

But this stops working if the server is restarted. I also tried running the command with the local account with which the agent was configured but it doesn't work either.

[LachlanWainwright]

Hi @marceloctorres 

Based on where us poor souls can't even get the agent to start 😁  Monitor 2025 Agent service not starting on server 

Maybe change the logging to see what comes up when the agent is started, these are @JeffMertzXcel instructions.  I have just changed to the agent exe, bolded bit.

Something might appear that could help....

PS C:\Users\Administrator> cd \
PS C:\> cd esri
PS C:\esri> cd .\ArcGIS\Monitor\Server\bin\
PS C:\esri\ArcGIS\Monitor\Server\bin> $env:LOG_LEVEL='debug'
PS C:\esri\ArcGIS\Monitor\Server\bin> .\arcgis-monitor-agent.exe --serve

Also, just poking about, try running some of these to see what appears that may help....

Note, this is for a working 2024.1.1 agent,
  arcgis-monitor-agent.exe -help