Search the VMware Knowledge Base (KB)
View by Article ID

vSphere Client 4.1 displays multiple windows with the error: A internal error occurred in the vSphere Client. Details: Object reference not set to an instance of an object (1033560)

  • 41 Ratings

Symptoms

  • After upgrading vCenter Server and vSphere Client to 4.1 258902, and when using the vSphere Client connecting to vCenter Server, several windows appear randomly with the error:

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

  • The viclient.log file may contain errors similar to:

    [viclient:Error :M: 6] 2010-09-23 10:21:53.272 UnhandledCallbackError in NotifyUpdates for server https://vcenter.usa-ed.net/sdk
    System.NullReferenceException: Object reference not set to an instance of an object.
       at VpxClient.VMList.UpdateCPUAndMemUsageForViewableItems()
       at VpxClient.VMList.OnUpdate(FilterUpdateArray fUpdates)
       at VirtualInfrastructure.Updates.PollerDispatcherImpl.NotifyUpdates(Map`2 handler2Updates)
    [VICnMngt:Critical:M: 6] 2010-09-23 10:21:53.272 OnServiceEvent UnhandledCallbackError for https://vcenter.usa-ed.net/sdk : Object reference not set to an instance of an object.
    [ :ShowExcp:M: 6] 2010-09-23 10:21:53.272 Error: An internal error occurred in the vSphere Client.
    Details: Object reference not set to an instance of an object.

  • This occurs on many vSphere Clients on many different Windows machines.
  • This issue may still occur even after removing vSphere Client, .NET Framework, and registry entries and reinstalled vSphere Client 4.1.
  • The vSphere Client installed on vCenter Server connecting to itself (vCenter Server) also shows similar symptoms.

Resolution

This issue is resolved in vCenter Server 4.1 Update 2. To download  vCenter Server 4.1 Update 2, see the VMware Download Center.
 
To work around this issue when you do not want to upgrade to vCenter Server 4.1 Update, replace VIClient.dll on all affected workstations.
 
Note: This workaround applies only to vCenter Server 4.1 GA, and not to vCenter Server 4.1 Update 1.
 
To replace VIClient.dll:
  1. Extract VIClient.dll from VIClient.7z (attached to this article) to a temporary location.

    Note: You may need to download the 7-Zip tool from http://www.7-zip.org/.

  2. Ensure that no vSphere Client sessions are currently running. Terminate all sessions.
  3. In the Windows Installation Drive (usually C:), go to Program Files\VMWare\Infrastructure\Virtual Infrastructure Client\4.1\.
  4. Locate the file named VIClient.dll and rename it to VIClient_Orig.dll.
  5. Copy the extracted VIClient.dll to Program Files\VMWare\Infrastructure\Virtual Infrastructure Client\4.1\.
  6. Restart the vSphere Client.

Additional Information

If the issue persists, file a support request with VMware Support and note this KB article ID in the problem description. For more information, see Filing a Support Request in My VMware (2006985) or How to Submit a Support Request.

Tags

vsphere-client-errors

See Also

Update History

12/07/2011 - Added information that this issue is resolved in vCenter Server 4.1 Update 2

Attachments

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 41 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 41 Ratings
Actions
KB: