Standalone Setup - No remote targets have yet been set up

OS Name/Version: Windows Server 2019

Product Name/Version: AMP 2.4.1.2

Problem Description: I updated ADS01 to 2.4.1.2 and it is now empty and only shows No remote targets have yet been set up.

[16:46:19] [GSMyAdmin Info]       : Starting AMPService version 2.4.1.2 (Halimede), built 21/12/2022 17:54
[16:46:19] [GSMyAdmin Info]       : Stream: Mainline (Release) - built by CUBECODERS/buildbot on CCL-DEV
[16:46:22] [GSMyAdmin Warning]    : Current time zone is set to Eastern Standard Time - It is recommended you switch to UTC+0 to avoid time-zone related issues
[16:46:22] [GSMyAdmin Info]       : OS: Windows / x86_64
[16:46:22] [GSMyAdmin Info]       : CPU: Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz (8C/16T)
[16:46:22] [GSMyAdmin Info]       : AMP Instance ID: f18a6d09-2bc6-4aac-85a3-496978e8cd46
[16:46:25] [System Warning]       : Assembly Newtonsoft.Json was loaded for Core via fallback handler, check plugin dependencies.
[16:46:26] [GSMyAdmin Info]       : Loaded ADSModule version 1.0.0.0 by CubeCoders Limited
[16:46:26] [GSMyAdmin Info]       : Loaded FileManagerPlugin version 1.0.0.0 by CubeCoders Limited
[16:46:26] [GSMyAdmin Info]       : Loaded EmailSenderPlugin version 1.0.0.0 by CubeCoders Limited
[16:46:26] [GSMyAdmin Info]       : Loaded WebRequestPlugin version 1.0.0.0 by CubeCoders Limited
[16:46:27] [GSMyAdmin Info]       : Loaded LocalFileBackupPlugin version 1.0.0.0 by CubeCoders Limited
[16:46:27] [GSMyAdmin Info]       : Loaded CommonCorePlugin version 1.0.0.0 by CubeCoders Limited
[16:46:27] [GSMyAdmin Info]       : ADSModule requests dependency InstanceManagerPlugin...
[16:46:27] [GSMyAdmin Info]       : Loaded InstanceManagerPlugin version 1.0.0.0 by CubeCoders Limited
[16:46:27] [GSMyAdmin Info]       : ADSModule requests dependency SystemUserManagerPlugin...
[16:46:27] [GSMyAdmin Info]       : Loaded SystemUserManagerPlugin version 1.0.0.0 by CubeCoders Limited
[16:46:28] [GSMyAdmin Info]       : Loaded steamcmdplugin version 1.0.0.0 by CubeCoders Limited
[16:46:28] [Core Info]            : Metrics server started OK on port 12820
[16:46:28] [GSMyAdmin Info]       : ADS startup complete in 606ms
[16:46:28] [ADS Info]             : Updating remote source CubeCoders/AMPTemplates
[16:46:28] [ADS Info]             : Updating existing remote source https://github.com/CubeCoders/AMPTemplates.git...
[16:46:29] [FileManager Notice]   : Using keypair with fingerprint ieAk1ChMTC5p4vf769citXT31rmojZBr5eQOUwGf03U=
[16:46:29] [FileManager Info]     : SFTP Server started on 0.0.0.0:2223
[16:46:29] [GSMyAdmin Info]       : Websockets are enabled.
[16:46:29] [GSMyAdmin Info]       : Webserver started on http://0.0.0.0:8080
[16:46:29] [WebServer Warning]    : RouterTimer@10Hz with 2 jobs started
[16:46:29] [GSMyAdmin Info]       : Checking for AMP updates...
[16:46:32] [GSMyAdmin Info]       : AMP is up-to-date.

Steps to reproduce:

  • Run “ampinstmgr -u ADS01”
  • Launch the WebGUI via the shortcut or browser
  • See “No remote targets have yet been set up.” with no options

Actions taken to resolve so far:

*Downloaded ampsetup.exe and reran.
*Changed to Nightly and updated
*Switched back to Mainline
*Reboots after stream changes and updates
*Ran “ampinstmgr --nocache --upgradeall”
*All command run inside an elevated cmd

Empty your browser cache.

Same result. I even tested in multiple browsers on 2 different internet connections, and still see the same thing.

I did find that one of the drives in my raid array are dying, so working on replacing that now.

Try two separate things…

  1. Run the ampsetup.exe again but choose Custom and make sure your datastore path is correct.
  2. In CMD run ampinstmgr repairto try and re-add the missing instances.

I attempted those fixes, and still get the same result

“ampinstmgr repair” results in tell me that there are no instances to import. If I launch AMP without ADS01, where it shows me the old interface, all my instances are there.

If you press f12 and look at the browser error logs, does anything show up?

I figured it out. The roles file is the cause. I made a new instance and tested moving the users and roles over to it. Users worked fine; roles caused the same issue.

I’m just going to rebuild the roles and see if that helps.