Unable to register one specific host (Monitor 2024.1/2025)

Question

Hi,

I'm having trouble registering one specific host, having succeeded with 6 others within the same network. That inability started in with Monitor 2024, and has persisted in Monitor 2025 (having upgraded yesterday).

Perhaps the strangest part is that it doesn't appear to be a communications issue between the host/agent and Monitor Server, as authentication succeeds, i.e. I receive the '[ success ] Successfully authenticated to ArcGIS Monitor Server' message, but no second message confirming registration. All other hosts register within a few seconds. I've left this one trying (maybe? or maybe it's failed quickly and just sitting there) for hours without any change.

The Monitor logs show no relevant warnings/errors, and I've not been able to find anything in the lower levels (though it's hard to see through the noise). Nothing obvious in Event Viewer on either the agent or server machines either.

Looking at the agent IDs of the registered hosts there is a gap, i.e. it's 1,2,3,4,6,7, so I tried registering as an existing agent (5), but that fails.

Our production portal, datastore, and hosting server reside on this host.

Any recommendations or things to check much appreciated.

Tim_White · Answer

Thanks for the suggestion @TimoT - in my case both hosts that register successfully and the problematic host are set to Domain.

TimoT · Answer

I encountered a similar issue previously. The problematic host's Windows network profile was set to Public instead of Private, causing slightly different firewall rules to apply.

Tim_White · Answer

Thanks for the response, Steven. Unfortunately there's no difference in firewall rules for this server than those that are registering without issue.

Another thought I had was some kind of conflict in the config-store, so I had the profile of the service account running the agent removed from the server and started over with a reinstall, but no change.

The gap in the registered agent ID's suggests to me that it's getting part of the way there, and the authentication succeeding (and that success being reported back to the agent host) makes it seem like the servers are communicating without issue, so I'm not sure where else to look.

I hadn't seen the post but did have the same licensing issue initially, and fixed it in the same way once I saw the keycodes file in the License24.0 folder getting updated.