VMware

This Question is Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
3 Replies Last post: Oct 28, 2009 8:54 AM by huttj  

Plugins wont load in vSphere client posted: Jul 7, 2009 11:47 AM

Click to view Partridge's profile Enthusiast 36 posts since
Jul 3, 2007

I'm having a difficult time getting plugins to load in the vSphere client on my workstation. I've cleaned out all installations of VMware software, and then reinstalled vSphere client to be sure that I am working in a clean environment. Connections at this point work fine, however if I attempt to load the plugin from SamplePlugin_40.zip none of it's extenions appear in the GUI, and it is not listed in the plugin manager.

Also, we've ported our VIClient plugin from 3.5 to vSphere, but when I load that on my workstation the tabs for inventory items do not appear. Instead I get a white panel saying "Required vSphere Client support files are missing. Restart vSphere Client to download and install missing files.". This works fine on other hosts, but fails on mine so I'm trying to isolate the location of the failure, such as a PATH conflict. Checking the vSphere Client output with Visual Studio doesn't indicate much though, it doesn't even look like the plugin is being loaded.

I am running vSphere Client 4.0.0 Build 162856. Has anyone else experienced either of these issues or can provide some insight. Thanks.

Re: Plugins wont load in vSphere client

2. Sep 22, 2009 12:00 PM in response to: Partridge
Click to view LeeTheMC's profile Novice 9 posts since
Sep 2, 2008
To anyone from VMware who is monitoring this thread or community,

Has VMware recognized and agreed that this is a problem? And is it (or will it) be documented officially on any support page? And finally, is there any fix possible from the vSphere Client side (to tolerate these quotes in the PATH variable)? Thank you.

Lee

Re: Plugins wont load in vSphere client

3. Oct 28, 2009 8:54 AM in response to: Partridge
Click to view huttj's profile Lurker 1 posts since
Nov 3, 2008

I filed a support request with VMware about this exact issue about a month ago. VMware engineering was previously aware of this issue and has noted that the earliest we will see a fix is in U2 for vCenter 4 sometime mid 2010. Until then, the only workaround is to manually remove quotes from the system path.


Developer Social Media

Communities