Upgrade from 2023.3.3 to 2025.1

Question

Hello,

I am trying to upgrade Monitor from 2023.3.3 to 2025.1 and am becoming deeply frustrated with the process. I have been following this guide to the letter...it does not seem like it should be that difficult. I confirmed that the underlying pgsql database is a supported version and created a backup. The installer for Monitor Server 2025.1 works fine and eats my authorization file, but then I encounter this error when trying to log in:

Even better, when I go and look at the installation directory on my D drive, it looks like basically nothing is there. Folders are extremely skimpy and don't have contents. I assume that is what the error is about..I think the folder, contents, or whatever from 2023.3.3 was not migrated to 2025.1. That's just a guess

I think something is deeply wrong with the installation process, even though the upgrade is said to complete 'successfully'. I attached what I think is an error log that looks fairly horrendous when you start parsing through it. Please help, I have no idea what is going wrong during the installation; this is causing our team a lot of headache.

arcgis-monitor-server-service.err.log

Bryan_Wade_0-1743095718362.png

ChrisBerryman · Answer

We had the same issue and worked with support and had no luck.  Tried upgrading 3 times before we just trashed our db and started over.. going through the process now of retuning all alerts, labels, collections etc.

DerekLaw · Answer

Hi @GrantSmith122 ,

Please contact Esri Tech Support and open a case so they can help you investigate your upgrade issue. It's difficult to assist without getting more detailed information about exactly what you did to perform the upgrade process.

>  Is that a database parameter that I need to remove before upgrading?

Nope this is not part of the upgrade process.

GrantSmith122 · Answer

So, after thinking about this more, I'm circling around the underlying pgsql database as the source of the problem. I took a look at the script that I used to originally create my agm database back when I deployed Monitor 2023; the script contains a line:

ALTER DATABASE agm SET search_path TO "$user", public;

I'm just guessing, but that looks somewhat related to the error message that I'm seeing. In the documentation for deploying Monitor 2024 or 2025, that piece of code/query is not there anymore. Is that a database parameter that I need to remove before upgrading? It seems like it might not be used/necessary anymore?