Hi ,
I have been waiting for 2024.0.1 as i have encountered the following issue
After upgrading from a previous version of ArcGIS Monitor Server to version 2024.0, the database may appear to be disconnected, and you may see the message "The database is not ready. Database schema is not up to date". Follow the steps below to complete the upgrade process
Currently i am running version 2023.3 and when trying to upgrade to 2024.0.1, the upgrade finishes successfully however, the web application fails to boot.
I have just two internal ports up and running which are 30001 och 30002. they should be two more ports opening which are 30003 and 30443 as i am enforcing https only. Anyone having the same problem?
I have tried upgrading 2023.3 to 2024.0 firstly and in this point i got no issue with the appserver, it was just the database issue as expected and then when trying to upgrade from 2024.0 to 2024.0.1 i got the issue with the appserver. I have even tried to upgrade from 2023.3 to 2024.0.1 directly and i got encountered the same issue.
i suspect that the issue has to do with the license, is there a specific license for 2024.0.1 because i used the same license for 2024.0?
Thanks in advance
//Anas
The license is the same for 24.0 and 24.0.1, so I don't think that is the issue. Follow the steps below:
1. Stop the AGM Server OS service.
2. Open a Powershell prompt on the AGM Server machine as the OS account running the AGM Server service.
3. Change directories to the AGM Server installation directory (C:\Program Files\ArcGIS\Monitor\Server\bin by default).
4. Run the AGM Server binary with debug logging enabled:
> $env:LOG_LEVEL='debug'
> ./arcgis-monitor-server.exe --serve
5. Let the software boot for about 30 seconds.
6. Copy the output from the terminal and provide it in a direct message to me.
Thanks,
Josh
Hi @JoshG
I have sent you now the output of the terminal
It seems that my database is missing a column which is components_view.agent_id
//Anas
What was the resolution? I am also waiting to upgrade to 2024.0.1 and wondering what the path is.
If you have a collection whose expression references an agent ID field, the collection must be removed before upgrading and recreated post-upgrade.
Josh
Hi @i3Admin ,
I would like to add one more detail. The agent ID did not exist anymore as it was deleted. it was the collection which was using the agentID in its expression that makes the upgrading process to fail. When i removed the collection and tried the upgrade again it works like a charm. the validation process is great but quite involved in the booting process of the monitor server it seems to be
//Anas