Problem with VUM "fault.PatchIntegrityError.summary"

[vm-sa]

Hell!

I have two hosts (hp dl380 g4) with ESX server 3.5 + storage HP MSA 1000 + server for VC

there is no problem with first server updates (now it has 84374 build)

but when i try to update another one, i receive message:

[http://images.people.overclockers.ru/156200.gif]

VMware Update Manager had a failure

fault.PatchIntegrityError.summary

i make fresh install from CD ESX 3.5 update 1 on this server, but receive this message againe

i install VC on another server, uninstall old VC, add host to new server, but nothing change in my problem

search does not give me any idea.... please help me GURU !!! :_|

[Robert_Murphy]

Good afternoon;

Ran into the same issue. From another community response found that the time on the ESX server was too far off. I reset the time and configured the NTP and it appeared to resolve the issue.

Murphy

[VVince]

HI,

i just tried to use VUM, and i've got the same message, but all my servers (both ESX 3.5i and VC) are using NTP and are on the same date&time

do you have any idea where i can find details about this error (in some logs for examples), i have the same problems on all my ESX servers (i have 6)

thanks for your help

Vincent

[Robert_Murphy]

Sorry Vincent, I didn't look for any errors once it started working. My

Update Manager is running on a different Windows Server than VC. I did

validate the times on all systems, especially the ESX servers from the

"Time Configuration" on the Configurations tab. I also validated the

time on the VC. That was about it. I have since moved to installing

the patches manually.

I basically pull all the one's I need from VMware to a Linux server,

unzip them, and Secure Copy (SCP) them to the /tmp/updates folder. A

quick command "esxupdate -n update" and away it goes. Simpler than 3.0x

was.

I keep finding issues with the Update Manager. I'll wait for the next

release.

One other thing you might want to try. From "time configuration" turn

off ntp client and set the time manually for all ESX servers and

manually for the Windows Servers. Try again. If it works great, and if

not, return it to it's original configs.

Good luck.