Resolving vCenter unable to synchronize with hosts and all VMs become orphaned error

I've encountered below error (vCenter unable to synchronize and all guest VMs become orphaned) yesterday. All VMs are working fine that time.
Login to each host and checked but each host are OK and all guest VMs are running well.

The error is appear on vCenter only. Checked from vSphere Client and Browser was appeared same error.

I try to PING each host IP and Name from vCenter Server.
Just got reply from IP and no reply from PING with name.
Yes, I realized it is DNS issue. vCenter unable to resolve each host's name.

I tried to flush vCenter Server DNS cache by using "ipconfig /flushdns" command via Command Prompt and restart the server once task done.

I login to vCenter after it restarted and noticed that vCenter able to sync with all host and all VMs also back to normal.

This kind of error can be happen in many situation.
but I just share how to resolve because of for other people who encounter same situation like me will not waste their time by reading this post.

Have a good time.
(Be knowledgeable, pass it on then)

How to solve VMware View Virutal Machine deployment fails with a purple diagnostic screen and the error: PF Exception 14 - GFCPutSectionHeader (2076931)?

When using VMware ESXi 5.5 to deploy VMware View machine with SE spare disk:
  • Host fails with a purple diagnostic screen as below and
  • You see this backtrace in the purple diagnostic screen and in the system logs as below

What will you do then?

2015-01-06T15:09:07.842Z cpu3:32848)@BlueScreen: #PF Exception 14 in world 32848:CmdCompl-3 IP 0x41802f0a5db1 addr 0x6c
2015-01-06T15:09:07.842Z cpu3:32848)Code start: 0x41802e400000 VMK uptime: 137:10:13:26.272
2015-01-06T15:09:07.843Z cpu3:32848)0x41240141da00:[0x41802f0a5db1]GFCPutSectionHeader@esx#nover+0x1 stack: 0x41240141da80
2015-01-06T15:09:07.843Z cpu3:32848)0x41240141daa0:[0x41802f0b7332]SEResource_UnlockResources@esx#nover+0x13a stack: 0x41240141dae0
2015-01-06T15:09:07.843Z cpu3:32848)0x41240141dac0:[0x41802f0bb60d]SETxnGTEFaultCleanupCompletionArgs@esx#nover+0x65 stack: 0x0
2015-01-06T15:09:07.844Z cpu3:32848)0x41240141db00:[0x41802f0bb65e]SETxnGTEFaultCompletion@esx#nover+0x4e stack: 0x410a7bd54cc0
2015-01-06T15:09:07.844Z cpu3:32848)0x41240141db40:[0x41802f0ace4f]SESparseCheckAndReleaseLocks@esx#nover+0x10b stack: 0x41240141dbc0
2015-01-06T15:09:07.844Z cpu3:32848)0x41240141db70:[0x41802f0afa6f]SESparseAsyncDataDone@esx#nover+0x43 stack: 0x4132c1e7d2c0
2015-01-06T15:09:07.845Z cpu3:32848)0x41240141dba0:[0x41802e42d29f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x410c3f360fb0
2015-01-06T15:09:07.845Z cpu3:32848)0x41240141dbd0:[0x41802e6ce2c2]FS_IOAccessDone@vmkernel#nover+0x56 stack: 0x412ec00e8b18
2015-01-06T15:09:07.845Z cpu3:32848)0x41240141dc00:[0x41802e42d29f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x412ec1b31480
2015-01-06T15:09:07.846Z cpu3:32848)0x41240141dc30:[0x41802e42d48f]AsyncCompleteOneIO@vmkernel#nover+0x16b stack: 0x412ec23e6080
2015-01-06T15:09:07.846Z cpu3:32848)0x41240141dc60:[0x41802e42d29f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x41240141dc90
2015-01-06T15:09:07.846Z cpu3:32848)0x41240141dc90:[0x41802e6fe241]FDSAsyncTokenIODone@vmkernel#nover+0xdd stack: 0x1022
2015-01-06T15:09:07.847Z cpu3:32848)0x41240141dd90:[0x41802e7214c3]SCSICompleteDeviceCommand@vmkernel#nover+0x46f stack: 0x410a7bd32488
2015-01-06T15:09:07.847Z cpu3:32848)0x41240141ddc0:[0x41802ed0bebe]nmp_CompleteCommandForDevice@com.vmware.vmkapi#v2_2_0_0+0x82 stack:
2015-01-06T15:09:07.847Z cpu3:32848)0x41240141ded0:[0x41802ed0c18e]nmp_CompleteCommandForPath@com.vmware.vmkapi#v2_2_0_0+0x12a stack: 0
2015-01-06T15:09:07.848Z cpu3:32848)0x41240141df60:[0x41802e742475]SCSICompletePathCommand@vmkernel#nover+0x2a5 stack: 0x41240141dfa0
2015-01-06T15:09:07.848Z cpu3:32848)0x41240141dfd0:[0x41802e7552c0]SCSICommandCompletionWorld@vmkernel#nover+0x19c stack: 0x0
2015-01-06T15:09:07.848Z cpu3:32848)0x41240141dff0:[0x41802e653532]CpuSched_StartWorld@vmkernel#nover+0xfa stack: 0x0
2015-01-06T15:09:07.853Z cpu3:32848)base fs=0x0 gs=0x418040c00000 Kgs=0x0

No need to worry so much about that.

VMware already mentioned that is well known issue for all versions of VMware ESXi 5.5 prior to Patch 02.

By updating to Patch 02 will resolve the issue.


For more details, please read articles from VMware below,

Have a good day.
(Be knowledgeable, pass it on then)