vCenter

Hello,

I am getting the following error. The client is on Windows 2008 R2. I have tried several different compatibility modes.

2010-09-28 09:40:08.758 System.IO.FileNotFoundException: Could not load file or assembly 'VpxClientCommon, Version=4.1.0.0, Culture=neutral, PublicKeyToken=7c80a434483c7c50' or one of its dependencies. The system cannot find the file specified.

at SmService.Main.AddExtension(String managedObjectType)

at SmService.Main.Load(VIApp viApp)

at VpxClient.Plugins.PluginManager.LoadPlugin(PVE pve, PluginInformation info, List`1 pluginServices)

2010-09-28 09:40:08.758 Plugins2.DiscoverPlugins processed directory (C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\SMS) 00:00:01.6213717

Unfortunately, it doesn't tell me the actual file but the path indicatred has these files in it:

SMS.dll

yFilesAdapter.dll

yFilesAlgorithms.dll

yFilesViewer.dll

Any thoughts? I read somewhere about a PATH being set with quotes but that isn't my issue.

I have the same problem. on my windows7 workstation. If i start the vsphere client on the Vcenter Server the storage monitoring plugin works just fine.

and I have the exact same problem as described above, plugin fails to load running vsphere client on win7 professional, but loads fine in vsphere client on the vcenter server.

Well I think I have a possible answer.

I had been playing around with 4.1 in a lab environment, and updated the vSphere client.

Then logging onto our production environment (4.0) the said monitoring plugin fails to load in the client. Downgrading the client and it works again.

http://www.boche.net/blog/index.php/2010/10/18/vcenter-storage-monitoring-plug-in-disabled/

[i]Jason Boche, VCDX #34, VCAP4-DCA, VCPx3, vEXPERT[/i]

[boche.net - VMware Virtualization Evangelist|http://www.boche.net/blog/][/i]

[VMware Communities User Moderator|http://www.vmware.com/communities/content/community_terms/][/i]

[Minneapolis Area VMware User Group Leader|http://communities.vmware.com/community/vmug/us-central/minneapolis][/i]

[vCalendar|http://www.boche.net/blog/index.php/vcalendar/] Author[/i]

My workstation is Windows 7 64b.

Since I have to work with all vSphere versions and following other post instructions,I've installed vi client versions in order. First 2'5U6, then 4.0U2, then 4.1. Even so when coneccting to v4.0 storage monitoring plugin hangs.

So Until a solution is published by vmware and Thanks to JasonBoche post this is a "old manual way" workarround:

save both versions (4.0.0.12305 and 4.1.0.12319) of the SMS.dll on the "C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\SMS" directory, and rename it when needed before conecting.

The limitation: take care that multiple conections to vSphere sesions must be done of the same version, (did not tried to mix them, just in case)