ADS01 webinterface broken after upgrade from 2.4.3.0 to 2.4.3.6

OS Name/Version: Windows Server 2022 - 21H2

Product Name/Version: 2.4.3.6 - standalone installation

Problem Description: ADS01 webinterface broken after upgrade from 2.4.3.0 to 2.4.3.6

Steps to reproduce:

  • upgrade via “ampinstmgr --nocache upgradeall”
  • start ADS01 instance → started → webinterface not running
  • webinterface wont load

Actions taken to resolve so far:

-stopped all instances, ran “ampinstmgr --nocache upgradeall” again
-restarted host


latest AMP logs file - no file found with any errors:

[04:31:20] [AMPService Info]      : Starting AMPService version 2.4.3.6 (Decadeus), built 07/05/2023 00:16
[04:31:20] [AMPService Info]      : Stream: Mainline (Release) - built by CUBECODERS/buildbot on CCL-DEV
[04:31:20] [AMPService Info]      : Running in a VMware environment.
[04:31:20] [GSMyAdmin Warning]    : Current time zone is set to W. Europe Standard Time - It is recommended you switch to UTC+0 to avoid time-zone related issues
[04:31:20] [AMPService Info]      : OS: Windows / x86_64
[04:31:20] [AMPService Info]      : CPU: Intel(R) Xeon(R) CPU E3-1275 v6 @ 3.80GHz (2C/2T)
[04:31:20] [AMPService Info]      : RAM: 8191MB
[04:31:20] [AMPService Info]      : AMP Instance ID: HIDDEN

ampinstmgr ShowInstancesTable output:
[Info] AMP Instance Manager v2.4.1.2 built 21/12/2022 17:55
[Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
Instance Name      │ Friendly Name    │ Module     │ IP              │ Port  │ Up
───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼───
←]8;;http://127.0.0.1:8080/ADS01             ←]8;; │ ADS              │ ADS        │ 0.0.0.0         │ 8080  │ √

netstat -aon → shows nothing running with listen port 8080


I can still see "AMPCache-Mainline-2430.zip" beside "AMPCache-Mainline-2436.zip" in my instance folder, is there a way to rollback to this version which was working?

This issue has already been resolved - running ampinstmgr --nocache upgradeall (Again, even if you already did it once since a new build was shipped - followed by a reboot if still not working on Windows) will resolve it.

Also you’re running AMP Instance Manager 2.4.1.2 - you should update that at some point soon :slight_smile:

1 Like

well well well, its indeed working now, thanks :smiley:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.