VSphere Client error - Pops up randomly

[spf62]

Here are my specs.

Virtual Center Server - ver 4.1.0 x2 (1 for production vm's, 1 for dev and test vm's)

Virtual Center Client - ver 4.1.0

several clusters with HA/DRS/DPM enabled

We recently installed to new Virtual Center servers, shortly after we started getting these errors. There isn't any consistency when these errors pop up.

"An internal error occurred in the vSphere Client
Details: Object reference not set to an instance of an object"

[a_p_]

Where do you get this error? On the vCenter Server itself or on clients with the vSpehere Client installed.

If on clients, are there any plugins (e.g. Update Manager, ...) installed which have not been updated yet?

You say you installed new vCenter Servers, however with the configuration you mention I assume you migrated the database. Can you confirm this and which DB do you use?

André

[spf62]

We get the errors on the clients only, and it's not all the time, it's totally random. But we all get them.

Some of us have all the plugins, some do not

New SQL server, New Database

[spf62]

We are all up to date with Client and VCS, using 4.1 Update 1 on both. All plugins installed

We all still get these errors randomly. But when they start they just keep coming and coming.

Everything is still functional in Virtual Center, this is more of an annoyance that anything.

[Howiedog]

Hi spf62,

I was having the same issues, and for me "random" ment that this error would pop-up anytime I was shutting down or firing up one of my VM's.

My problem was that I had removed a "Xangati" VM, but the plug-in was still "enabled".

Disabaled the plug-in and now those errors no longer appear.

Check to see if you removed a vm that also has a plug-in referenced to it.

Hope that helps?

Howard

[canvcp]

It happens to my environment as well. I noticed this a lot after 4.1 Update 1. Usually it pops up after powering on the suspended VMs. It is really annoying and VMs seem work just fine.

Is there any update for this issue? thanks in advance.

[spf62]

We are still struggling with this. It pops up so randomly. But once it starts it will not go away until we close out the client and go back in

[mark_chuman]

We were told this has to do with old plugins / client versions installed on the machine getting errors.  Has anyone seen this on a completely new machine with only the 4.1 client version ever installed?

[spf62]

Yes.. we have a few clients that installed 4.1 fresh, and still get the error messages occassionally. Very frustrating.

[A_Mikkelsen]

Found the solution here

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=103356...

came from the thread

http://communities.vmware.com/message/1675234

A. Mikkelsen