Alright, we’ve hit a classic paradox: you need permissions to gain permissions.
At this point, it seems like there might be a consistency issue with the AMP configuration or a deeper issue at the user role level. Let’s proceed with a more drastic approach to reset permissions manually:
-
Stop ADS:
ampinstmgr stop ADS01 -
Manually Edit the ADS Configuration:
- Locate the
ADS01configuration file, typically found within your AMP directory (likely inC:\AMP\Instances\ADS01). - Open
AMPConfig.confor equivalent for your instance with a text editor.
- Locate the
-
Set the Permissions Manually:
- Look for the sections related to roles and permissions.
- Manually ensure that the “admin” role has all necessary permissions, including
GSMyAdmin.WebServer.SetConfigandSession.Exists. Add them if they are missing.
-
Start ADS:
ampinstmgr start ADS01
These steps should force the needed permissions update. Keep in mind, directly editing config files isn’t normally recommended but should help reset things.
Finally, try modifying the port settings again in ADS after performing the above steps. If this still doesn’t work, we may need a fresh reinstallation to ensure no corrupted configs are hindering you.
Give it a go and let’s break this loop! ![]()