If you see any of these errors when trying to activate your property on staging or production:
Property validation failed. Please retry or contact your account representative.
Property validation failed: one or more files are already pending activation. Please retry after that activation completes.
there might be a conflict in a system managing property activation records. It should resolve itself after a few minutes, so you can retry the activation in 30 minutes.
If the issue persists, contact Akamai Professional Services for help for further investigation, including this information:
- property name,
- property version you're working on,
- the network you are trying to activate on (staging or production).
Unable to perform validation at this time. that appears when you're trying to activate your property on staging or production might be caused by:
- a new property hostname being added to your property,
- a presence of special characters in your account name, such as
- Fast Activation being enabled,
- connectivity issues on the user network,
- a property hostname using a public suffix.
To fix the problem:
- Make sure the domain isn't already in use under a different account where it's mapped to an edge hostname in a DNS record.
- Verify the list of ASCII characters allowed in account names. If your account name uses an unsupported character, contact Akamai technical Support to have this changed.
- Make sure Fast Activation is disabled.
- Try the activating from a different client network.
- Make sure your hostname doesn't contain a public suffix.
- Try activating your property again.
If you have checked all of the possible causes but the problem persists, contact Akamai Professional Services for help.
If you're trying to edit a property hostname or add a new one and can't see a desired edge hostname in the dropdown list, this might mean you don't have access to the group this edge hostname belongs to. If the edge hostname was created in top level group but your property is in a sub-group, your access is restricted only to that sub-group and the edge hostname won't show in the list for your configuration.
Contact Akamai Professional Services for help. They can either move the edge hostname to your sub-group or grant you access to the top level group that contains the edge hostname.
You try to edit a property and experience one of these problems:
- You get
The name chosen already exists for this grouperror when trying to create a property.
- Your new property isn't listed in the group, and you can't create a new one with the same name as the system says that such property already exists.
- You receive an
Access Denied – no Edit accesserror after cloning an existing property with a new name and trying to save it.
These errors might appear if:
- you cloned your property from another property,
- you migrated your property between contracts, or moved between groups/sub-groups,
- you have insufficient permissions granted in Identity and Access Manager (IAM),
- you have a locked behavior to your property. This can happen if you duplicated a rule that contains a locked behavior that was originally added by <Akamai internal users.
If your property should be listed in a sub-group:
- In Control Center, go to Account Admin > Identity & Access.
- Click the Resources tab, select the correct sub-group, and click Manage.
- Add the property to the sub-group. If the property already exists under the sub-group, contact Professional Services.
If the error was triggered by a locked behavior, contact Professional Services. Locked advanced features can only be edited by Akamai internal users. They can assist you to either remove the problematic behaviors or save the property on your behalf.
If you see this error:
You must have the 'Enhanced TLS' module on your contract to select a hostname with an Enhanced Certificate. You must either add the 'Enhanced TLS' secure modules to your contract or choose a non-secure hostname., this means you don't have the contract line item required to use Enhanced TLS certificate to secure your property.
Property Manager compares the type of certificates available in Certificate Provisioning System (CPS) with the options available in your contract. If you attempt to use HTTPS with your CPS-managed certificate without having the related module in your contract, the error is triggered.
To use your Enhanced TLS certificate, make sure you have the required module added to your contract and contact Professional Services for help.
If you have the related module in your contract, but the error appears, clone your property and verify if Customer Certificate is listed in the security options. If it's there, enable this option and errors shouldn't appear any more.
Updated 4 months ago