Issues in Push and Rollback
| Error Message | Possible Cause | Possible Solution |
|---|---|---|
| Error while establishing SSH connection. | AppViewX is not able to establish a SSH connection using the given credentials. | Provide valid credentials to communicate with the device. |
| Unable to parse configuration to fetch currently associated data. | AppViewX may not be able to fetch and parse the content of the certificate which is already associated. | Check if AppViewX has permissions for fetching the existing certificate content. |
| No server certificate is found | AppViewX may not be able to fetch and parse the content of the certificate which is already associated. | Check if AppViewX has permissions for fetching the existing certificate content. |
| Exception while downloading trust store / Exception while parsing certificate | AppViewX is not able to download the trust store from the server. | Check if AppViewX has permission to download the trust store from the device. |
| Certificate and/or key missing | Certificate provided in the push request might be invalid. | Check if the certificate that is being pushed is valid. |
| Unsupported Key Algorithm | Key algorithm of the certificate is not supported by the server. | Provide a valid key algorithm that is supported by Weblogic servers. |
| Push cannot be performed automatically for the Keystore type 'DemoIdentityAndDemoTrust'. Kindly customize the keystore locations in the connector. | Customize push location not provided during push operation. | Provide a location to push the certificate inside the server. |
| Parsing a certificate is failed | Certificate content might be invalid. | Check the certificate content. |
| Exception while writing file to avx local. | AppViewX may not have access to the local/export directory. | Check if AppViewX has permission for the local/export directory. |
| Certificate push is failed. |
Invalid location provided. User is not having permission to push file to the location. |
Check the location provided is valid. Check if the user has permission to access the location. |
| Unable to perform Bind for the server. | Server may not be running in the given address and port. | Check if the server is running in the given port and listen address |
| Unable to open edit session for the server. | AppViewX is not able to communicate with the server. | Check if the server is up and running and the server credentials are valid. |
| Unable to perform edit for the server. | AppViewX is not able to communicate with the server. | Check if the server is up and running and the server credentials are valid. |
| Unable to save the current changes made to the server. | AppViewX is not able to communicate with the server. | Check if the server is up and running and the server credentials are valid. |
| 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 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. |
| Push not triggered or succeeded or No existing data available for backup process. | Rollback couldn’t proceed because push was not successful. | Only successfully pushed certificates can be rolled back. |
| 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. |