Upgraded, renamed, or created a new vCenter, now all jobs are failing/disabled. (4047472)

User created a new vCenter server or renamed vCenter server. Jobs are that were associated with the vCenter server no longer run.

Jobs may be associated with a vCenter server. If something is associated with a vCenter server and that vCenter server is no longer available for any reason, the jobs will fail. Creating a new vCenter server in vRanger will not fix the jobs. Jobs are associated with the old vCenter server in the vRanger database and the old vCenter server is no longer available.

Use extreme caution when editing the database. If you are unsure, please open a support case and obtain assistance before continuing.

The workaround is to edit the database entry for the old vCenter server and to point that database entry to the new vCenter server.

1. If you have added a new vCenter server, remove it from your vRanger inventory.

2. Download and install the SQL Express 2005 Management Studio. This is available in 32 and 64 bit versions from Microsoft. The download page is at: http://www.microsoft.com/download/en/details.aspx?id=8961

3. Open the Management Studio and connect to the vRanger database. To do this, Expand the Databases folder, then expand vRangerPro

4. Expand Tables, right-click the dbo.InventorySourceConnection table, and select Open Table.

5. Locate the entry for your old vCenter server. vCenter servers will have a 0 in the InventorySourceConnectionTypeID field. and the name of the old server should be in the Address field.

6. Edit the Address field for the old vCenter server to point to the new vCenter server.

7. Scroll to the far right-hand table, labeled IsDeleted. If the IsDeleted field for the old vCenter server is True, edit it to change it to False.

8. Restart the vRanger services or reboot the vRanger server.

9. After rebooting the server, verify that the new vCenter server appears in the Inventory. Re-enable any jobs that were disabled as a result of the vCenter change.