Common causes for application deployment failure

Last Updated : Nov 23, 2020 |

If the application is not reachable from System Manager Solution Deployment Manager or Solution Deployment Manager Client, the OVA deployment fails at the sanity stage, because you might have:

  • Provided an IP which is not on the network.

  • Provided wrong network values that causes the network configuration for the application to not work properly.

  • Chosen a private virtual network.

The following are some examples of wrong network values and configuration that can result in the OVA deployment failure:

  • Using an IP which is already there on the network (duplicate IP).

  • Using an IP which is not on your network at all.

  • Using a DNS value, such as 0.0.0.0.

  • Deploying on an isolated network on your VE deployment.

You can check the deployment status in the Current Action Status column on the Applications tab.