Error Messages

Error Message	Possible Cause	Possible Solution
Unable to initiate request.	Pushing to device when certificate is unavailable, i.e, in a new state. Previous work order is in progress and not completed. AppConnector might not be in sync.	Push to device after certificate has been retrieved from CA. Initiate push after previous work order is finished. Synchronize the AppConnector and retry.
Unable to initiate request, template is in disabled state	Given workflow is not in the enabled state.	Enable the push/rollback workflow from the Workflow section.
User is not authorized	User does not have required permissions to push to the device.	Retry after getting the access for required action.
Private key content is unavailable.	Private key content is not available for the certificate.	Private key is mandatory for the certificate to be pushed.
Application connector(s) not found	Application connector info was not found.	Provide the correct connectorId if not pushing using AppViewX UI.
Request associated with the application connector is in progress	Previous work order is in progress and not completed.	Initiate this request after the previous work order is finished.
Certificate not found.	Pushing to device when certificate is unavailable, i.e, in a new state.	Push to device after certificate has been retrieved from CA.
Certificate push failed. Error is, jdk.nashorn.internal.runtime.Undefined	Private key content is not available for the certificate.	Private key is mandatory for the certificate to be pushed.
Certificate push failed	Check internet /Proxy connection is provided in AppViewX node.	Login to AppViewX portal and provide proxy details in Menu->Settings->General->Proxy.
`{"code":"Forbidden","message":"The user, group or application 'appid=d6dde692-94d9-4a9c-8bd4-77782d22b0ef;oid=669e113f-0651-4bb5-9698-cd4e863e1ee9;numgroups=0;iss=https://sts.windows.net/e5f90d85-3cdf-457d-a611-1aca82b0843b/' does not have Certificates import permission on key vault 'keyvault-type-1;location=eastus'. For help resolving this issue, please see https://go.microsoft.com/fwlink/?linkid=2125287","innererror":{"code":"ForbiddenByPolicy"}}`	Azure Keyvault instance doesn’t have certificate Import permissions in access policies.	Login to Azure portal and navigate to Azure KeyVault -> Access policies and check the Certificate management Operations having Import permission.
`{"code":"Forbidden","message":"Client address is not authorized and caller is not a trusted service.\r\nClient address: 125.21.72.158\r\nCaller: appid=d6dde692-94d9-4a9c-8bd4-77782d22b0ef;oid=669e113f-0651-4bb5-9698-cd4e863e1ee9;iss=https://sts.windows.net/e5f90d85-3cdf-457d-a611-1aca82b0843b/\r\nVault: keyvault-type-2;location=eastus","innererror":{"code":"ForbiddenByFirewall"}}`	Azure Keyvault Network blocking the Certificate Push.	Login to Azure portal and navigate to Azure KeyVault -> Networking and check the Firewalls and virtual networks if IP is allowed to access the Keyvault.

Unable to initiate request.

Pushing to device when certificate is unavailable, i.e, in a new state.
Previous work order is in progress and not completed.
AppConnector might not be in sync.

Push to device after certificate has been retrieved from CA.
Initiate push after previous work order is finished.
Synchronize the AppConnector and retry.

Unable to initiate request, template is in disabled state

Given workflow is not in the enabled state.

Enable the push/rollback workflow from the Workflow section.

User is not authorized

User does not have required permissions to push to the device.

Retry after getting the access for required action.

Private key content is unavailable.

Private key content is not available for the certificate.

Private key is mandatory for the certificate to be pushed.

Application connector(s) not found

Application connector info was not found.

Provide the correct connectorId if not pushing using AppViewX UI.

Request associated with the application connector is in progress

Previous work order is in progress and not completed.

Initiate this request after the previous work order is finished.

Certificate not found.

Pushing to device when certificate is unavailable, i.e, in a new state.

Push to device after certificate has been retrieved from CA.

Certificate push failed. Error is, jdk.nashorn.internal.runtime.Undefined

Private key content is not available for the certificate.

Private key is mandatory for the certificate to be pushed.

Certificate push failed

Check internet /Proxy connection is provided in AppViewX node.

Login to AppViewX portal and provide proxy details in Menu->Settings->General->Proxy.

{"code":"Forbidden","message":"The user, group or
                                application
                                'appid=d6dde692-94d9-4a9c-8bd4-77782d22b0ef;oid=669e113f-0651-4bb5-9698-cd4e863e1ee9;numgroups=0;iss=https://sts.windows.net/e5f90d85-3cdf-457d-a611-1aca82b0843b/'
                                does not have Certificates import permission on key vault
                                'keyvault-type-1;location=eastus'. For help resolving this issue,
                                please see
                                https://go.microsoft.com/fwlink/?linkid=2125287","innererror":{"code":"ForbiddenByPolicy"}}

Azure Keyvault instance doesn’t have certificate Import permissions in access policies.

Login to Azure portal and navigate to Azure KeyVault -> Access policies and check the Certificate management Operations having Import permission.

{"code":"Forbidden","message":"Client address is
                                not authorized and caller is not a trusted service.\r\nClient
                                address: 125.21.72.158\r\nCaller:
                                appid=d6dde692-94d9-4a9c-8bd4-77782d22b0ef;oid=669e113f-0651-4bb5-9698-cd4e863e1ee9;iss=https://sts.windows.net/e5f90d85-3cdf-457d-a611-1aca82b0843b/\r\nVault:
                                keyvault-type-2;location=eastus","innererror":{"code":"ForbiddenByFirewall"}}

Azure Keyvault Network blocking the Certificate Push.

Login to Azure portal and navigate to Azure KeyVault -> Networking and check the

Firewalls and virtual networks if IP is allowed to access the Keyvault.