Forums Archived

This forum has been archived. No new posts can be made and no new users can sign up. It remains here for reference only.

Find the new forums here

ADS Not Upgrading with AMP Installer

  • 530 Views
  • Last Post 29 January 2022
Combustabl3L3mon posted this 27 January 2022

Hello, I've followed a few of the posts I've seen on here for upgrading my ADS and AMP instances, but it doesn't seem to be fully working. I've download the most recent installer and run it, then restarted my computer, and the web portal still tells me I need to update. I ran ampinstmgr upgradeall and it updated all of my instances, but not ADS. I cannot manage any of my instances now since they are on the new version by my portal(?) or AMP itself is not. I ran ampinstmgr table and get this:

[Info] AMP Instance Manager v2.3.1 built 13/01/2022 21:17
[Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
Instance Name      │ Friendly Name    │ Module     │ IP              │ Port  │ Up
───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼───
TimmyAndDevon      │ Timmy And Devon  │ Minecraft  │ 127.0.0.1       │ 8081  │
SMP                │ SMP              │ Minecraft  │ 127.0.0.1       │ 8082  │
SMPTest            │ SMP Test         │ Minecraft  │ 192.168.0.140   │ 8083  │
Test               │ Test             │ Factorio   │ 192.168.0.140   │ 8084  │

But the support section of the web portal says:

Application Name    AMPService
Application Version     2.3.0.6
Release Stream  Release
Build Date  02/12/2021 15:36

So I'm a bit confused.

I also tried backing up my data, uninstalling the program and installing it again, but it still isn't updated somehow. I don't want to do a complete uninstall via revo unless I can be walked through how to import my servers and settings again.

This is set up on a Windows 10 Home computer under a non-admin user like the guide says. Any help is appreciated.

Thanks in advance

Order By: Standard | Newest | Votes
Combustabl3L3mon posted this 29 January 2022

I've figured it out. I uninstalled AMP. I then uninstalled the services that were created by AMP using command prompt, and appended my AMPDatastore with .old for safekeeping. Restarted the PC, installed AMP from scratch and set everything up again. I then realized that when you create the initial instance for ADS, it asks if you would like to have it start on startup. If you choose yes, it creates it as a service, and you are unable to uncheck the box. It either starts it up as a service or it doesn't. It is also selected that way be default (which is probably why I didn't think anything of it).

I then created my instances for each server. I found that I could copy my old instances on top of them if I named them identically, then restart my computer and they would take. All I had to edit was the server port and the IP choice. This might be something good to look into. It's weird that it can't start at boot unless it's a service, as all it takes to do that is a simple .bat file with some code like this:

@echo off
echo loading AMP...
ampinstmgr startall
echo press any key to continue...
pause

Either way, this is still some great software and I appreciate your help in troubleshooting this!

Combustabl3L3mon posted this 28 January 2022

I'm also now realizing this moved the database location to a different hard drive (probably the one that AMP wants instead of what I want). Is there any easy way to change this while avoiding what happened previously?

Combustabl3L3mon posted this 28 January 2022

Okay, that seems to have resolved my issue. Any guesses on how that happened since I only used default settings the whole time? (With the exception of choosing to have database stored on a different drive letter) Also, I no longer see 3 of my 4 server instances. Is there a way to add them back in?

Thanks a million! :)

Mike posted this 28 January 2022

Looks like you don't have an ADS instance at all, which means you may well have hosed your installation at some point. My guess is you incorrectly used the GUI to convert game instances into services which is the wrong thing to do.

Run ampinstmgr quickstart then once that's done run ampinstmgr repairauth standalone http://localhost:8080

Combustabl3L3mon posted this 28 January 2022

What other information can I get for you for more troubleshooting?

Combustabl3L3mon posted this 28 January 2022

I have already, many times. It seems that was generated some time ago. I forgot to look at the time stamp. I'm still unable to manage my instances.

Mike posted this 28 January 2022

Ah, reboot the system then xD

Combustabl3L3mon posted this 27 January 2022

I found this in a file named 'LastAMPException.txt'. Let me know if this helps:

[Error] --- Begin Exception Data ---
[Error] OS: Windows (x86_64/None)
[Error] Module: ADSModule, Version: AMPService 2.3.0.6
[Error] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
[Error] Instance ID: 0782fd77-3e55-462f-b7b7-cf2b733b20b1
[Error] SocketException
[Error] [0] (SocketException) : Only one usage of each socket address (protocol/network address/port) is normally permitted
[Error]    at Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at Net.Sockets.Socket.Bind(EndPoint localEP)
   at Net.Sockets.TcpListener.Start(Int32 backlog)
   at m.Http.HttpBackend.ConnectionLoop()
[Error] --- End Exception Data ---
[Warning] Last error was raised less than 60 minutes ago, error report will not be submitted.

Combustabl3L3mon posted this 27 January 2022

I posted this in the original post, but the status command gives me:

[Info] AMP Instance Manager v2.3.1 built 13/01/2022 21:17
[Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
Instance Name      │ Friendly Name    │ Module     │ IP              │ Port  │ Up
───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼───
TimmyAndDevon      │ Timmy And Devon  │ Minecraft  │ 127.0.0.1       │ 8081  │
SMP                │ SMP              │ Minecraft  │ 127.0.0.1       │ 8082  │
SMPTest            │ SMP Test         │ Minecraft  │ 192.168.0.140   │ 8083  │
Test               │ Test             │ Factorio   │ 192.168.0.140   │ 8084  │

I've tried it with all of them shutdown, but ADS still doesn't get updated. What is the name of the field I'm looking for to find what ADS is called? I've tried ADS, Minecraft, AMP Instance Manager, AMPService, and CCL-DEV but it seems that none of those refer to ADS in a way the upgrade command recognizes it.

I've also tried stopping all of the instances and then stopping all of the Services and running upgradeall, but it still seems to not upgrade ADS.

Mike posted this 27 January 2022

on Windows it'll probably have a different name - run ampinstmgr status to check.

You should also fully shut down AMP by running ampinstmgr stopall and checking task manager.

Combustabl3L3mon posted this 27 January 2022

Running ampinstmgr upgrade ADS comes up with:

C:\Users\AMP>ampinstmgr upgrade ADS
[Info] AMP Instance Manager v2.3.1 built 13/01/2022 21:17
[Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
[Error] No such instance matching name: 'ADS'

I've also cleared my browser's cache which doesn't help either.

Combustabl3L3mon posted this 27 January 2022

I was wondering if it's possible that there's just a file somewhere that it's just not updating that "tells" it what version it is and it isn't changing it, since the command reads back as the correct version but the web portal says it's still the previous one. I had tried reinstalling it without clearing files and it still reads as the old version. Is there something like this I could try?

Combustabl3L3mon posted this 27 January 2022

I've done this already. It results in:

[Info] AMP Instance Manager v2.3.1 built 13/01/2022 21:17
[Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
[Info] Upgrading instance TimmyAndDevon
[Info] Using cached archive: H:\AMPDatastore\Instances\AMPCache-2310.zip
[Info] Upgrade successful
[Info] Upgrading instance SMP
[Info] Using cached archive: H:\AMPDatastore\Instances\AMPCache-2310.zip
[Info] Upgrade successful
[Info] Upgrading instance SMPTest
[Info] Using cached archive: H:\AMPDatastore\Instances\AMPCache-2310.zip
[Info] Upgrade successful
[Info] Upgrading instance Test
[Info] Using cached archive: H:\AMPDatastore\Instances\AMPCache-2310.zip
[Info] Upgrade successful

I've also done it with the nocache argument and I've also cleared out the folder that stores the file so it can download it again, restarting every time I've done this, and it still results in ADS not being updated.

Mike posted this 27 January 2022

Open a command prompt and run ampinstmgr upgradeall

Live Chat Register to post
Categories
Search
Popular Tags
Hot Topics
Close