Update Manager Error after Update 2

[michaelb23]

Hello all,

I have updated to 3.5 Update 2 and have seen several posts where people have had issues with installing Update Manager. I did not have any issues installing the Update Manger, but now after I open the VI Client and use it for approx 5-6 hours I receive the message "Your session with the VMWare Update Manager Server is no longer valid. The VMware Update Manager Client plugin will be unloaded from VI Client". This has only started happening after Update 2. Is there a "timeout" value somewhere that I should be looking for?

Mike

Sorry, I should also say that I updated to the newest version of VirtualCenter also (Build 104215). Not just ESX 3.5.

[chris]

I'm seeing the same thing since the upgrade from VC2.5u1 to VC2.5u2.

[Amphire]

same here... quite annoying...

running vi client on vista x64 (no aero though since the vi client absolutely crawls with aero turned on, ALSO quite annoying)...

[s1m0nb]

Same here - any updates

[AntonVZhbankov]

I already contacted support - they said it's a know bug and they're going to fix it.

[oturn]

We are seeing the same problem.

[richardt]

Hello,

I have the same problem and have a call into vmware support via dell, the reply so far is :

They have said that it’s a new issue with the same problem of database not accessible with VC 2.5 U2.

Currently they are liasing with their engineering team to provide feedback regarding this solution.

They have said it may take some time with no fix eta for their engineering team to find the fix.

Meanwhile if VMWARE tech support can locate any workaround after looking at the logs I would update you once received.

I wouldn't hold your breathe for a quick fix :smileysad:

Rich

[Buck76]

Same problem here... additionaly slow performance in Update Manager after Update 2 installation

[Larry Hedrick]

It seems that everythign is very slow adter the upgrade to u2. Also, my patch management works ok but trying to patch a host seems to take hours...

[michaelb23]

Just an update to this issue. I called tech support and they believed the issue was due to a corrupt database. First, we reinstalled VUM without reinitializing the database and still the same issue. Second we reinstalled VUM and this time DID reinitialize the UPDATE MANAGER database. This database is separate from the ESX database. After the reinstall of VUM (and reinitializing) the updates automatically started downloading. I am not sure how long this took to download as it was late in the day and I went home. The next morning all updates had downloaded and I have not had the error since.

Mike

[senseipetz]

Only for better understanding. It can't be a workaround the reinitialize the Database, because we got the same problem and we have the same problem again. It should be somewhere else. The issue is also existing. We have an Oracle 9i enviroment and this was so many times reinitialized, that the DB himself doesn't know how many times.