Select to view content in your preferred language

New version of application already installed.

294
4
04-09-2025 10:54 AM
LouEarly
Occasional Contributor

After upgrading an agent to 2024.1.1 The following errors pop up anytime someone logs on to that machine.  I've attempted to unregister the agent, uninstall and reinstall with no success.  

 

 

Capture.JPG 

 

Capture.JPG

4 Replies
DerekLaw
Esri Esteemed Contributor

Hi @LouEarly,

I've attempted to unregister the agent, uninstall and reinstall with no success.  

To confirm that you've completely removed AM Agent from the machine, after running the uninstaller wizard,

Can you please navigate to C:\Program Files\ArcGIS\Monitor in Windows Explorer and ensure the folder labeled "Agent" is completely removed? Then try to install AM Agent again.

Hope this helps,

 

 

 

LouEarly
Occasional Contributor

Uninstalled using the wizard and removed the C:\Program Files\ArcGIS\Monitor directory.  Reinstalled and still experience the same issue.

0 Kudos
DerekLaw
Esri Esteemed Contributor

Hi @LouEarly,

Can you please check this location for any older ArcGIS Monitor release files?

C:\Users\arcgis\AppData\Local\ESRI\ArcGISMonitor 

And you'll need to remove them before attempting to install Monitor again.

Hope this helps,

0 Kudos
TylerTheobald
Emerging Contributor

I manually ran the 2024.1.1 installer over the existing 2024.1.0 install and did not experience your issue.  

From the screenshots, it appears that this is a Windows Installer issue where the SCCM task didn't completely unregister the app and there are some orphaned registry entries.  

With 15 year of app deployment experience, I can say this is where I end up going to the old Microsoft "Windows Installer Cleanup" utility which can be found out there in download archives (since Microsoft no longer supports it) and removing the orphaned app install registration through that tool. 

Try manually installing the new agent on another server next time without a deployment tool and verify you don't get this behavior, and then you'll know if this is an Esri issue or your deployment tool is at fault.