topic Re: Error connecting to DB after 2024.0 upgrade in ArcGIS Monitor Questions

Error connecting to DB after 2024.0 upgrade

WhitneyLoy — Tue, 27 Aug 2024 21:27:01 GMT

Getting the following error after upgrading to 2024.0. The Database is not ready. Database schema not up to date

I have tried restarting both the ArcMonitor and PostgreSQL service and reinstalling the update and the same error is occurring.

Re: Error connecting to DB after 2024.0 upgrade

EdenPunter — Tue, 27 Aug 2024 23:40:11 GMT

Same issue in my organization after upgrading. Have restarted the ArcGIS Monitor Server and PostgreSQL services also.

Re: Error connecting to DB after 2024.0 upgrade

NicholasEverdell — Tue, 27 Aug 2024 23:43:17 GMT

We are also seeing this error after upgrading from 2023.1 in our environment.

Re: Error connecting to DB after 2024.0 upgrade

BrendaButton — Wed, 28 Aug 2024 02:53:50 GMT

Our 2023.1 Environment is also experiencing these issues.

Re: Error connecting to DB after 2024.0 upgrade

GeoJosh — Wed, 28 Aug 2024 13:03:24 GMT

Hi @WhitneyLoy and @EdenPunter,

Are you also upgrading from 2023.1 --> 2024.0 or are you upgrading from another version? Dev team is investigating.

Thanks,

Josh

Re: Error connecting to DB after 2024.0 upgrade

WhitneyLoy — Wed, 28 Aug 2024 17:01:18 GMT

@GeoJosh CORRECTION I am upgrading from 2023.3.1

Re: Error connecting to DB after 2024.0 upgrade

EdenPunter — Wed, 28 Aug 2024 21:43:59 GMT

@GeoJosh upgrading from 2023.3.1

Re: Error connecting to DB after 2024.0 upgrade

BrendaButton — Thu, 29 Aug 2024 06:50:50 GMT

My department is also upgrading from 2023.3.1, apologies

Re: Error connecting to DB after 2024.0 upgrade

Dan_Brumm — Thu, 29 Aug 2024 15:17:25 GMT

we upgraded from 2023.3.1, same issue...rolled back

Re: Error connecting to DB after 2024.0 upgrade

Joshua-Young — Thu, 29 Aug 2024 19:08:28 GMT

I am getting the same error message. Upgrading from 2023.3.1 to 2024.0.

Re: Error connecting to DB after 2024.0 upgrade

WhitneyLoy — Fri, 30 Aug 2024 20:48:46 GMT

Support was able to assist me getting the db back online.

Re: Error connecting to DB after 2024.0 upgrade

NiG — Tue, 03 Sep 2024 12:38:23 GMT

I encountered the same problem and resolved it by removing the old database schema (AGM) and then recreating it. I lost everything on that DB, but at least its working now.

CREATE USER agm WITH PASSWORD '<password>'

NOSUPERUSER

INHERIT

NOCREATEDB

NOCREATEROLE NOREPLICATION;

CREATE DATABASE agm WITH OWNER=agm;

GRANT ALL ON DATABASE agm TO agm;

ArcGIS Monitor system requirements—ArcGIS Monitor | Documentation

Re: Error connecting to DB after 2024.0 upgrade

DavidColey — Tue, 03 Sep 2024 14:39:46 GMT

Hello @WhitneyLoy - can you report here what support did to help you get the db back online? Did you have to go through the same steps as @NiG - removing and then recreating the agm database?

Re: Error connecting to DB after 2024.0 upgrade

GeoJosh — Tue, 03 Sep 2024 15:52:40 GMT

Hi everyone. The development team has identified the issue and provided the solution to Esri Support. I also want to provide the solution here for those who are comfortable running SQL commands against PostgreSQL databases. If you do not have experience administering PostgreSQL, please reach out to Esri Support for help performing this workflow.

The cause of this issue is the presence of empty Analysis Views or Analysis Views that only contain Header elements. The solution to this issue is to remove all empty Analysis Views and restart the ArcGIS Monitor Server process.

If you have already rolled back to a previous release, you can simply delete any empty Analysis Views through the web GUI and then re-run the upgrade. If your ArcGIS Monitor installation is stuck in the state described in this post, you can manually delete the Analysis Views from the database. To do so:

Stop the ArcGIS Monitor Server service.
Connect to the ArcGIS Monitor database in pgAdmin.
Open a new query window.
Issue this query: SELECT * FROM ANALYSES
Take a CSV backup of the results.

6. Delete any row where the expressions array under the configuration column is empty or is missing entirely. For example, a row with the configuration object below would be deleted, because the expressions array is [] (empty):

7. Start the ArcGIS Monitor Server service and try accessing the application again. If the problem persists, please reach out to Esri Support for further troubleshooting.

Alternatively, a patch that addresses this issue will be available in the coming weeks.

Josh

Re: Error connecting to DB after 2024.0 upgrade

DavidColey — Tue, 03 Sep 2024 18:23:13 GMT

Hi @WhitneyLoy and @NiG - clearly Josh's reply/solution(s) below render my question moot, but thanks anyway

Re: Error connecting to DB after 2024.0 upgrade

AnasKanaan — Mon, 09 Sep 2024 11:41:34 GMT

Hi @GeoJosh ,
I do not have a problem with the configuration column in the analyses table. my log is saying The database is not ready. Database schema not up to date. I upgraded from 2023.1 to 2024
Many Thanks buddy 🙂
//Anas

Re: Error connecting to DB after 2024.0 upgrade

RexNeville — Tue, 01 Oct 2024 16:39:16 GMT

No one should use Monitor 2024.0 it has other bugs with no patch released. wait for 2024.1.

Re: Error connecting to DB after 2024.0 upgrade

DerekLaw — Tue, 01 Oct 2024 17:56:19 GMT

HI @RexNeville,

FYI, ArcGIS Monitor 2024.0.1 is planned for release on Oct 3rd.

Hope this helps,

Re: Error connecting to DB after 2024.0 upgrade

JeffMertzXcel — Sat, 26 Oct 2024 03:13:37 GMT

This worked for me going to 2024.0.0 from 2023.3.1 . Additionally, I found that some components, specifically disk monitoring, did not upgrade. The state in the components table was set to 'migrated' and should have been 'monitored'. After updating them, they all showed up again in the Storage folder. See this post: Solved: Re: ArcGIS Server services missing after upgrading... - Esri Community

Re: Error connecting to DB after 2024.0 upgrade

GrantSmith122 — Mon, 29 Dec 2025 21:31:53 GMT

I am attempting to upgrade to Monitor 2025.1 from 2023.3.1 and am getting a similar error but I don't think it is related to the ANALYSES table ( I don't have an empty arrays).

I used command prompt and ran arcgis-monitor-server.exe admin:database:info to see if I could get some more database info, and this is the result I got:

I know this is kind of a ridiculous question, but does anyone know how to get the database schema ready? I think this could be the root cause of the issue.