# Installation Known Issues

### VMware Lifecycle Plugin hangs on Uploading

This is currently a known issue with the VMware plugin and currently the reason is unknown as to why this fails. Refer to Manually Uploading the Rubrik Plugin section and use either the Python or Bash steps to upload the plugin.

**Note**: If the plugin failed to upload you may need to manually remove the failed upload using the next section.

### Removing Failed Uploads in vCloud Director 9.5

If the plugin fails to upload, there may be elements of the plugin that need removed. Follow the steps to identified the failed plugin and remove:

Open the vCD API Explorer using the following URL:

```
https://myvcdcell.rubrik.com/api-explorer/
```

This will open a Swagger UI; using this we can now find the plugin and remove it.

Find the API for:

```
GET /extensions/ui
Get a list of all UI Extensions
```

Select the API and press `Try it out` and `Execute` (you may get a access denied, if so, login to vCloud Director first), once complete, it will return a JSON value; find the block that contains `"pluginName": "Rubrik"` e.g.

```
  {
    "pluginName": "Rubrik",
    "vendor": "Rubrik",
    "description": "vCD Extensibility Plugin",
    "version": "1.1.0",
    "license": "Proprietary",
    "link": "http://support.rubrik.com",
    "tenant_scoped": true,
    "provider_scoped": true,
    "enabled": true,
    "id": "urn:vcloud:uiPlugin:f70734f2-284a-436c-aae4-ab3e49f28ec4",
    "plugin_status": "ready",
    "resourcePath": "https://shrd1-vcd-cell.rubrikdemo.com/tenant/System/uiPlugins/f70734f2-284a-436c-aae4-ab3e49f28ec4/757f8ef5-0145-4e86-abde-6e31d37caa7f"
  }
```

Take the `id` value from this block e.g. `urn:vcloud:uiPlugin:f70734f2-284a-436c-aae4-ab3e49f28ec4`

&#x20;Next, we need to find the next API call to delete the plugin, browse in the Swagger UI to:

```
DELETE /extensions/ui/{id}/plugin
Delete the plugin for this extension
```

Select `Try it out` and then paste the ID value from above into the `id` field and select `Execute`

&#x20;This will return a `204` if successful.

Next we also need to delete the plugin from the System level, so find the final API in the Swagger UI:

```
DELETE /extensions/ui/{id}
Delete system level logo
```

Select `Try it out` and then paste the ID value from above into the `id` field and select `Execute`

&#x20;This will return a `204` if successful.

Proceed back to the Upload instructions to perform the upload again or refer to manually uploading the Rubrik Plugin if there are issues with \`VMware Plugin Lifecycle Management\`

### vCloud Director Provider Portal 503 errors after failed upload

vCloud Director can at time fail to upload a plugin file, which leaves the plugin in a partial state. This is due to the plugin being present in the vCloud Director Database and the files are missing from the appliance.

In order to resolve this, we need to remove the plugin from the vCloud Director backed Database. Below are the methods for removing this:

### SQL Server

**Note: Ensure there is a valid SQL Server Backup for this Database before running these steps**

Using SQL Management Studio, connect to the vCD Database Instance. Once logged in expand **Database**, your SQL Databse for vCD and finally **Tables.** Navigate down the list to find **dbo.ui\_plugin** - right click this table and select **Edit Top 1000 rows.**&#x20;

![](https://4095106604-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LhZl1ijzJsQtWdyQE3k%2F-M3D0ywdoUFFs_2NaZnc%2F-M3D3864jqIKc5upxQLW%2Fimage.png?alt=media\&token=3ad7d6e5-8ef1-4ee1-b998-f1ef52fedf30)

Select the row with the Rubrik Plugin (Check the version matches the plugin you most recently uploaded) and **right click** and select **Delete.** Confirm this is correct and press **Yes** to the delete the row.

![](https://4095106604-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LhZl1ijzJsQtWdyQE3k%2F-M3D0ywdoUFFs_2NaZnc%2F-M3D3NBcjuZkL9geC990%2Fimage.png?alt=media\&token=a631b41f-aa0b-48f8-a81e-cf95d05b5432)

Browse back to the **Provider** portal for vCD and ensure the 503 errors have disappeared and vCD is working as normal.
