Issues in Push and Rollback

Error Message Possible Cause Possible Solution
security.xml file read operation failed AppViewX may not be able to read security.xml of the profile. Check if AppViewX has permissions to read security.xml of the profile.
Config file parsing failed Configuration file might be corrupted/ empty. Verify if the configuration file is correct.
Insufficient information to fetch backup data available in the server. Configuration files fetched from the server may not have sufficient information. Check if the config file has all the information related to server configuration.
Unsupported bit length Bit length is not supported by the server. Provide a valid bit length that is supported by Websphere server.
Unsupported Key Algorithm Key algorithm of the certificate is not supported by the server. Provide a valid key algorithm that is supported by Websphere servers.
Creating local certificate file failed - <Detailed Message> AppViewX is not able to create file in a temporary folder. Check the detailed message to determine the remedy.
Server certificate is not available to push. Server certificate location may be invalid. Check if the trust store location is available.
Private Key doesnot exists for certificate Private key may not be available for the certificate. Check if the private key for the certificate is available.
Private key parsing failed for the certificate. Private key may be a invalid one. Check if the private key is valid.
Writing of converted certificate related files into file in AppViewX local directory is failed. AppViewX may not have permission to write a file in the export directory. Check if AppViewX has proper permissions for the export directory.
Certificate created date is earlier than server present time The starting of certificate validity period is earlier than the servers present time. The starting of certificate validity period should match with the server’s time. It should be greater than the server’s present time.
Unsupported Type Certificate format is not supported by the server. Check for the supported certificate formats.
Error found in wsadmin response The WSadmin console may not be working on the server. Kindly check WSadmin console is properly working or not
Unable to initiate request.

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

  2. Previous work order is in progress and not completed.

  3. AppConnector might not be in sync.

  1. Push to device after certificate has been retrieved from CA.

  2. Initiate push after previous work order is finished.

  3. 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.