This issue is caused by a sync issue with QRTZ and Inventory. It is easily remedied, however it will require down time as the cells will need to be shut down in the process. And don’t forget…BACKUP, BACKUP, BACKUP. You can never have too much backup 🙂 Just follow the steps below…
I was in the process of upgrading VC 6.0 EP01 to 6.0 U1 when I realized that the process to perform this same version upgrade was not the same. I did quite a bit of hunting for the specific info on how to do this, so I figure I would save people some time and publish the link here.
Follow the steps given below to capture OVFTool logs:
- Open vCD UI in browser by adding ?debug=true at the end. For example see URL: https://xx.xxx.xxx.xx/cloud/?debug=true
- Now reproduce the issue
- Collect the client logs from the client machine. If client machine is windows, then the logs will be at following location:
There are a couple items that can be easily missed in the Documentation for upgrading the VCSA in version 6. The documentation is located HERE.
Here is a quick step by step to help summarize:
There are a ton of blogs out there with complex queries and actions you can perform when your transaction logs are full and the vCD Web Interface fails with an error like:
.CellNotActiveException: Cell is not active
Well, I decided to make it simple for those who just want to get your environment back up and running ASAP.