2024.1.1+704
We created an incident record overnight (10pm - 5am) for the nightly maintenance window of servers and then we started getting fake/ghost connectivity alerts for all our Windows agents at the beginning and end of the maintenance window each evening. We get an email, but there are no actual connectivity alerts shown in the console and we know the servers aren't going down at the exact same time each night. So completely fake.
Removing the incident record did not solve the problem. Seems something is stuck in the database and I've got an active Esri case that has gone on for many weeks with resolution not getting any closer.
Reaching out to see if anyone has experience with this scenario.
Thanks!
Does it look like this?
ID | OPENED AT | CLOSED AT | STATE | STATUS | ALERT RULE | COMPONENT NAME | COMPONENT ADDRESS_INTERNAL | COMPONENT TYPE - SUBTYPE | METRIC NAME |
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | Database GIS_PROD | underdog-az | Database - SQL Server | Connectivity | ||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | Database - GIS_PROD_UTIL | underdog-az. | Database - SQL Server | Connectivity | ||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | UNDERDOG-AZ Relational ArcGIS Data Store | 10.0.5.11:9876 | ArcGIS Data Store - Relational | Connectivity | ||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | Production Server = GNASHER-AZ | ArcGIS Server | Connectivity | |||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | BITSY-AZ Image Server | 10.0.5.15 | Host - Windows | Connectivity | ||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | UNDERDOG-AZ Database | 10.0.5.11 | Host - Windows | Connectivity | ||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | AGO Janesville | ArcGIS Online Organization | Connectivity | |||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | ARGO-AZ Portal | 10.0.5.9 | Host - Windows | Connectivity | ||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | Production Portal = ARGO-AZ | Portal for ArcGIS | Connectivity | |||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | Image Server BITSY-AZ | https://fido-az /image | ArcGIS Server | Connectivity | ||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | GNASHER-AZ Server | 10.0.5.10 | Host - Windows | Connectivity | ||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | FIDO-AZ Web Adaptor | 10.0.5.14 | Host - Windows | Connectivity | ||
12/2/2025, 6:01:32 PM | Pending | Critical | Average < % % 100% | BRAIN-AZ VertiGIS | 10.0.5.7 | Host - Windows | Connectivity |
I have noticed that when I changed the database maintenance time, it directly coincided with the "connectivity" critical errors on all my ArcGIS Enterprise servers. Since AGO is one of my connected systems it reports a loss of connectivity too. I am using 25.0
-Steve
Hi @SGTomlins,
FYI, Josh is currently out of office and will not return back to work until mid-January.
@TylerTheobald and @SGTomlins,
Please contact Esri Tech Support and open a case so they can help investigate your issue.