Hi
OS: Windows Server 2019 Datacenter
I upgraded the Monitor agent to 2025 on 2 machines and neither agent service will start.
Agent installs without error and then when the service tries to start it stops immediately.
This machine worked and works for all other versions of the monitor agents and I reinstalled 2024.1.1 back and have no issues, fires on up.
Did all the usual stuff of unregistering, removing every reference in the install folder, the service account folder running it etc.
Nothing of relevance in Event Viewer
I am outta ideas, anyone got a thought?
I'll lodge a ticket with ESRI AU now and keep you all posted.
Please & thanks 😊
Lachlan
When I updated the log to append following these instructions XML Configuration file for winsw I get the following:
server names & ip addresses changed
arcgis-monitor-agent-service.err
*** xyzxy.x.x.au can't find 0.0.0.1: Non-existent domain
*** YYYYY.y.y.au can't find 0.0.0.2: Non-existent domain
arcgis-monitor-agent-service.out
Error:
Command
failed:
for
/f
"tokens=2
delims=:"
%a
in
('nslookup
0.0.0.1
^|
findstr
/B
Name:')
do
@echo
%a
***
xyzxy.x.x.au
can't
find
172.26.24.16:
Non-existent
domain
at execSync pkg/prelude/bootstrap.js:2115
⁃ Module._compile
pkg/prelude/bootstrap.js:1930
Error:
Command
failed:
for
/f
"tokens=2
delims=:"
%a
in
('nslookup
0.0.0.1
^|
findstr
/B
Name:')
do
@echo
%a
***
xyzx.x.x.au
can't
find
0.0.0.1:
Non-existent
domain
at execSync pkg/prelude/bootstrap.js:2115
⁃ Module._compile
pkg/prelude/bootstrap.js:1930
Solved! Go to Solution.
How should that help? We don't have public ip addresses on our VMs in azure...
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.
Same issue here after upgrading ArcGIS Monitor Server 2024 to 2025.
@DerekLaw Should I open a premium support ticket for us to track the issue?
Hi @LorenzMeyer1,
> Should I open a premium support ticket for us to track the issue?
Yes, please do. It's always helpful to collect information and data on issues. Thank you in advance.
Hi ,
I get the same behavior when we added https_proxy to system environment variable.
I could quit understand how you changed and updated the log to append following these instructions XML Configuration file for winsw.
It is possible for you so send me an example of what exactly to change?
thank you in advanced
Iris hadar
Add me to the issue too - all affected machines on my on-premises VM deployment have multiple NICS talking to multiple vLANS. Nslookup showing that It's attaching itself to DMZ NIC when it needs to be talking across the the VM NIC. DMZ is intentionally isolated and locked down route. It's not going to find anything by trying to traverse that path.
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,
Any update on this patch release date yet? We're having the same problem as others and have been without monitoring for more than 3+ weeks now. Looking forward to that patch. Thanks
Same!
Hi @MikeSchonlau and @CraigCarsley,
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,