TSM for VE 6.4 Plugin - FMM16016E An error occurred while connecting to the Derby DB

Came across an interesting issue recently in that I could no longer access the TSM for VE 6.4 plugin with the following error messages appearing:

Whilst this isn't disastrous as the TSM for VE schedules continue to run, it makes monitoring and reporting of environments a pain. TSM administrators have to revert back to utilising the dsmsched and dsmerror logs for the datamover nodes rather than the shiny plugin.

Ok so whats gone wrong? Last night my plugin was working fine and this morning it isn't. In rare cases, the vmcli database might get corrupted because the service.properties file is deleted or becomes corrupt. This can happen when the vmcli daemon process is killed while it is writing to this file. In this case, messages similar to the following example will appear in the vmcli log file:

FUNCTIONS 15:03:27,346 (daemon) #ERROR FMM16119E An error occurred trying to create the Derby DB.
com.ibm.storage.vmcli.exceptions.VmcliDBException: FMM16016E An error occurred while connecting to the Derby DB.

To resolve the issue you will need to restore the service.properties file located within C:\Program Files (x86)\Common Files\Tivoli\TDPVMware\VMwarePlugin\derby\VMCLIDB\ 

If you don't have a valid backup of the file or restoring the file does not resolve your issue uninstall the TSM for VE 6.4 plugin, manually delete the following directories C:\Program Files (x86)\Common Files\Tivoli\TDPVMware\VMwarePlugin & C:\IBM\tivoli\tsm\tdpvmware\ewas reboot the TSM for VE proxy and re-install the TSM for VE 6.4 plugin. You will now once again have a working TSM for VE plugin with a blank configuration. Open the vSphere Client re-launch the TSM for VE Plugin, re-run through the configuration wizard defining (not re-registering) the TSM Server, vCenter node, VCLI node, Datacenter nodes and Datamover nodes, re-validate the nodes and confirm all data i.e. backup schedules, reports e.t.c are once again visible via the TSM for VE 6.4 Plugin.