Unable to update ADS01 to 2.6.2.0

Steve_Slaney · 25 June 2025 11:47

Note - If you do not fill in every section below, your post won’t be answered - you must provide the steps you have followed so far and the actions you’ve already taken. Make sure to remove this notice from your post too.

Screenshots of text are prohibited. Always copy and paste text as text.

Make sure you search before posting! Duplicate posts for the same issue may not be answered.

OS Name/Version: Windows 11 Home / 24H2

Product Name/Version: Currently running version 2.6.1.2 - 20250325.1

Problem Description:

If you're sharing console output, logs, or commands you have run, please make sure to use code tags 
(3x backticks for blocks, 1x backtick for a single line) to help make posts readable. This also
provides syntax highlighting.

Steps to reproduce:

Tried updating via Console but get a page loading error
Tried updating via CMD but get an error
Read through blog posts and tried again. No luck
Tried submitting a ticket 3 times via the app but it seems to freeze and not post

Actions taken to resolve so far:
Apologies if this ticket has been sent multiple times, I wasn’t sure it was getting posted.

I am trying to update from v2.6.1.2 to v2.6.2.0 but whichever way I do it I get errors. If I try via the app its a page loading error and I have to log back into the app again. If I try via CMD I get the following errors.

C:\Users\Steve>ampinstmgr --nocache upgradeall
[Info/1] AMP Instance Manager v2.6.1.2 built 25/03/2025 12:57
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Stopping instance ADS01...
[Info/1] Waiting for instance to stop...
[Info/6] Instance ADS01 has stopped.
[Info/6] Supplied instance name is ambiguous.
[Error/6] No such instance matching name: 'ADS01'
[Info/6] Upgrading instance BuildTeam01
[Info/9] Downloading AMP from https://cdn-downloads.c7rs.com/AMP/Mainline/20250617.1/AMP_x86_64.zip...
[##################################################] ETA 00:00:00 @101.31 MiB/sec
[Info/6] Complete
[Info/17] Upgrade successful
[Info/17] Upgrading instance UHC01
[Info/16] Upgrade successful
[Info/16] Upgrading instance AC12101
[Info/16] Upgrade successful
[Info/16] Upgrading instance FC_1_2101
[Info/9] Upgrade successful
[Info/9] Upgrading instance FrilCraftCreative01
[Info/16] Upgrade successful
[Info/16] Upgrading instance AC1-2001
[Info/16] Upgrade successful
[Info/16] Upgrading instance SkyBlock01
[Info/16] Upgrade successful
[Info/16] Upgrading instance Minecraft01
[Info/6] Upgrade successful
[Info/6] Upgrading instance FrilCraft01
[Info/16] Upgrade successful
[Info/16] Upgrading instance S7D2D202501
[Info/17] Upgrade successful
[Info/17] Upgrading instance Roundabout101
[Info/9] Upgrade successful
[Info/9] Upgrading instance Border01
[Info/9] Upgrade successful
[Info/9] Upgrading instance Tunnel01
[Info/6] Upgrade successful
[Info/6] Upgrading instance Impossible01
[Info/6] Upgrade successful
[Info/6] Supplied instance name is ambiguous.
[Error/6] No such instance matching name: 'ADS01'
[Info/6] Upgrading instance S7D2D_Test01
[Info/17] Upgrade successful
[Info/17] Upgrading instance Rebirth01
[Info/17] Upgrade successful
[Info/17] Upgrading instance Subsistence01
[Info/6] Upgrade successful
[Info/6] Upgrading instance ACUpdateTester01
[Info/17] Upgrade successful
[Warning/17] Failed to register job process

A while ago I tried moving all the instances onto a newly installed D: drive and that caused a lot of issues, I’m not sure if thats the problem here.

Regards and thanks
Steve

Greelan · 25 June 2025 11:49

Follow this guide: How to update AMP to the latest version

Steve_Slaney · 25 June 2025 12:08

Hi, thanks for the quick reply. Before I follow your suggestion can I just confirm that you did actually read through my post. I really do apologise if you did but I dont want to go through the setup again if I can avoid it as that caused issues in the past and I’m pretty sure that is why I have this issue now. If the panel doesn’t allow me to update and CMD doesn’t allow me to either then I will but I’d also like to know why I get the error when an instance of ADS01 is clearly there.

Mike · 25 June 2025 12:12

If you run ampinstmgr status do you have multiple instances with the same name?

Steve_Slaney · 25 June 2025 12:14

Hi Mike. Yes I do and Im sure this is the problem but I have no idea how to sort it. I think I know how it happened but I’m a little afraid to start deleting them

ADS01              │ ADS              │ ADS        │ 0.0.0.0         │ 8080  │
UHC01              │ UHC              │ Minecraft  │ 127.0.0.1       │ 8081  │
BuildTeam01        │ BuildTeam        │ Minecraft  │ 127.0.0.1       │ 8082  │
AC12101            │ AC121            │ Minecraft  │ 127.0.0.1       │ 8083  │
FC_1_2101          │ FC_1_21          │ Minecraft  │ 127.0.0.1       │ 8084  │
FrilCraftCreati... │ FrilCraftCrea... │ Minecraft  │ 127.0.0.1       │ 8085  │
AC1-2001           │ AC1-20           │ Minecraft  │ 127.0.0.1       │ 8086  │
Rebirth01          │ Rebirth          │ Generic    │ 127.0.0.1       │ 8087  │
SkyBlock01         │ SkyBlock         │ Minecraft  │ 127.0.0.1       │ 8088  │
Minecraft01        │ AC Creative      │ Minecraft  │ 127.0.0.1       │ 8089  │
FrilCraft01        │ FrilCraft        │ Minecraft  │ 127.0.0.1       │ 8090  │
ADS01              │ ADS01            │ ADS        │ 0.0.0.0         │ 8091  │
S7D2D_Test01       │ S7D2D_Test01     │ Generic    │ 127.0.0.1       │ 8092  │
Roundabout101      │ Roundabout       │ Generic    │ 127.0.0.1       │ 8093  │
S7D2D202501        │ 7D2D2025         │ Generic    │ 127.0.0.1       │ 8094  │
Subsistence01      │ Subsistence      │ Generic    │ 127.0.0.1       │ 8095  │
Border01           │ Border           │ Minecraft  │ 127.0.0.1       │ 8096  │
Tunnel01           │ Tunnel           │ Minecraft  │ 127.0.0.1       │ 8097  │
Impossible01       │ Impossible       │ Minecraft  │ 127.0.0.1       │ 8098  │
ACUpdateTester01   │ ACUpdateTester   │ Minecraft  │ 127.0.0.1       │ 8099  │

Mike · 25 June 2025 12:18

So you’ve somehow ended up with two ADS01 instances. Interesting.

Make sure AMP is fully stopped, then manually edit Instances.json and remove the ADS01 instance on port 8091.

Steve_Slaney · 25 June 2025 12:35

Ok, done that. It was in the instances.json on the D: drive. I also note that there is an instances.json in the C: drive and both of them have ADS with port 8080

Mike · 25 June 2025 12:44

Is this an installation that has been moved between systems at some point? I don’t even see how it could get into its current state.

Steve_Slaney · 25 June 2025 12:49

Yes Mike. A while ago I had a larger D: drive installed and I wanted to move everything over. I tried and clearly failed to do that. Then I ran the AMPsetup again as suggested earlier and lots of stuff happened and most of it was bad. So now I have ADS with some game servers on the D: drive and ADS with other game servers on the C: Drive. I’d like them all on D: but as I mentioned, I’m very nervous about doing anything now since It’s clear I’ve made such a balls of it already.

C:\Users\Steve>ampinstmgr status
[Info/1] AMP Instance Manager v2.6.1.2 built 25/03/2025 12:57
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Instance Name      │ Friendly Name    │ Module     │ IP              │ Port  │ Up
───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼───
ADS01              │ ADS              │ ADS        │ 0.0.0.0         │ 8080  │
UHC01              │ UHC              │ Minecraft  │ 127.0.0.1       │ 8081  │
BuildTeam01        │ BuildTeam        │ Minecraft  │ 127.0.0.1       │ 8082  │
AC12101            │ AC121            │ Minecraft  │ 127.0.0.1       │ 8083  │
FC_1_2101          │ FC_1_21          │ Minecraft  │ 127.0.0.1       │ 8084  │
FrilCraftCreati... │ FrilCraftCrea... │ Minecraft  │ 127.0.0.1       │ 8085  │
AC1-2001           │ AC1-20           │ Minecraft  │ 127.0.0.1       │ 8086  │
Rebirth01          │ Rebirth          │ Generic    │ 127.0.0.1       │ 8087  │
SkyBlock01         │ SkyBlock         │ Minecraft  │ 127.0.0.1       │ 8088  │
Minecraft01        │ AC Creative      │ Minecraft  │ 127.0.0.1       │ 8089  │
FrilCraft01        │ FrilCraft        │ Minecraft  │ 127.0.0.1       │ 8090  │
S7D2D_Test01       │ S7D2D_Test01     │ Generic    │ 127.0.0.1       │ 8092  │
Roundabout101      │ Roundabout       │ Generic    │ 127.0.0.1       │ 8093  │
S7D2D202501        │ 7D2D2025         │ Generic    │ 127.0.0.1       │ 8094  │
Subsistence01      │ Subsistence      │ Generic    │ 127.0.0.1       │ 8095  │
Border01           │ Border           │ Minecraft  │ 127.0.0.1       │ 8096  │
Tunnel01           │ Tunnel           │ Minecraft  │ 127.0.0.1       │ 8097  │
Impossible01       │ Impossible       │ Minecraft  │ 127.0.0.1       │ 8098  │
ACUpdateTester01   │ ACUpdateTester   │ Minecraft  │ 127.0.0.1       │ 8099  │

ADS01 port 8091 has been removed. I’ve done another all stop and then ran a

ampinstmgr --nocache upgradeall

Everything appeared to update with no errors. I restarted the PC and and opened AMP but its still showing AMP Release “Phobos” v2.6.1.2, built 25/03/2025 13:02 in the panel.

This means I now get this error when starting game instances via the panel

This instance is running a newer version of AMP than this ADS instance. This instance is version 2.6.2.0 but this ADS instance is version 2.6.1.2. Please update this ADS instance.