VMware Update Manager plugin failures

December 8th, 2008 by jason Leave a reply »

Roger Lund posted several links on his blog which I was personally interested in because I have dealt with them in one way shape or form. One of them was a potential resolution to the issue where the VIC loses connectivity to VMware Update Manager and the VUM plugin unloads. The error message is “Your session with the VMware Update Manager Server is no longer valid. The VMware Update Manager Client plugin will be unloaded from the VI Client”

12-7-2008 9-19-21 PM

This is an issue that I wouldn’t say I’m plagued with, however, it does pop up every few days and the easy fix is to simply re-enable the VUM plugin. It’s an inconvenience that I wanted to get to the bottom of some day when I had time, but thus far it hasn’t been a high priority. I had checked the VUM logs but was not able to determine anything conclusive.

At any rate, I was excited to see the link on Roger Lund’s blog pointing to VMware KB article 1007099 “Update Manager Client is randomly disabled”. The link discusses a potential solution of disabling anti-virus scanning of the VUM repository (where all the code and metadata is downloaded to). I performed this over the weekend by neutering Symantec Antivirus Corporate Edition and kept my fingers crossed.

Things were looking good until Sunday night when the VUM error popped up again. Oh well, back to the drawing board. If anyone has any other ideas, I’m all ears.



  1. Dustin says:

    Hi Jason!

    Thanks for posting this. I, like you, have the same position on VUM where this is an annoyance more than a problem. However, as a consultant, this is more tricky to explain to customers.

    In any event, this problem happens in environments where there is no AV scanning nor malware scanning of any sort. It just unloads itself. I also don’t have the answer, but to me, this is not an AV issue.

  2. Roger Lund says:

    You could take a look at this post.

    Might be worth the read, but I know you cruze the forums more than I do.


    C:\Program Files\VMware\Infrastructure\Update Manager\vci-integrity.xml

    In those hostconfig section changed:


    were is the IP of the VC server.

  3. Steffen says:

    Thanks for posting about this issue, Jason (and Roger too). At my former employer we had the same “problem”, but never found a corresponding log file entry or anything else, which could have been responsible for the disconnection. Im still on the search for the solution, hopefully someone will soon solve the riddle…

  4. Vikanich says:

    You should change to
    in the C:\Program Files\VMware\Infrastructure\Update Manager\vci-integrity.xml

Leave a Reply