Hi All - I downloaded VSC 4.2 today and did an upgrade. After the install, the VSC Icon on the home page of Virtual Center is gone!. I looked in Control Panel and the 4.2 version is listed there. When I look in the Plug-In Manager GUI, I see the following (attached). I've unistalled and reinstalled the software. I get all the way to registering with Virtual Center, but yet, I'm unable to see the Icon in VC. I also notice multiple MethodFault.summary errors in the Recent Tasks.....
Anyone come across this? Any pointers? What happened.
Unfortunately, it's not clear from here what the root cause of the problem is. The second screenshot indicates that the VSC server is not running, so possibly, some error forced a shutdown. Take a look at these files (paths relative to the VSC installation directory) to determine what the error might be:
Also from the second screenshot, the version of the registered Virtual Storage Console plugin is 4.0 which indicates that the Virtual Storage Console service did not reach the point where it updated the extension with the vCenter Server. Did you register at https://localhost:8143/Register.html?
This typically happens when there is a network communication failure between the vCenter server and the VSC server... but it can be triggered by things like bad DNS, failing services, not enough RAM for JAVA (or heap allocated for JAVA).
I'd recommend the following:
Upgrade VSC to 4.2, VSC 4.0 has been deprecated and isn't compatible/likely to work with the version of ESX or vCenter you're running
make sure the min java heap is set to 1024, and max is set to 4096 (unless you have a huge environment then you can make these values larger)
Re-register the plugin on the vCenter server:
change both the "plugin" and vCenter from DNS entries to IP addresses
Restart the VSC server (or restart the Virtual Storage Console Service)
Close and reopen your vSphere client
wait (patiently) until the NetApp discovery tasks complete
If this action plan doesn't get it up and running, please give us a call at NetApp technical support to continue troubleshooting and we can help you review the logs to determine why the methodfaultsummary errors are happening during discovery.