Endpoint Protection

 View Only

  • 1.  Upgrading Error

    Posted Apr 28, 2023 04:02 PM

    Hi Team 

    I have a customer who has installed SEPM and he wants to upgrade to 14.3 RU_7 version. Now, when we execute the setup.exe, an error appears with the following message:

    - "The installer integrity check failed with error code 0x800b0004. Common causes for this failure include an incomplete download, damaged media, or problems with the Trusted Root certificate store"

    I have reviewed the certificates and all its ok, I have reinstalled the certificates and the error still.

    ¿Does anyone has had the same problem?



    ------------------------------
    [Presales Manager]
    [Once Soluciones]
    [Mexico]
    ------------------------------


  • 2.  RE: Upgrading Error

    Broadcom Employee
    Posted Apr 30, 2023 11:29 PM

    That particular error code I have seen only twice before. Both times it was happening during SEP client upgrades and we suspect it was due to some corruption or out-of-date content in the old product version already installed and not a problem with the new product installer. Removing the existing version allowed the new installer to run OK. This may not be a solution for a SEPM (SEP Manager), since customers usually wish to upgrade existing SEPM and migrate its database contents. If you wish to troubleshoot further please open a case with support.




  • 3.  RE: Upgrading Error

    Posted May 05, 2023 07:50 AM

    Could try a repair installation on the existing version installation (in lieu of removal) to attempt to repair any corrupted content.  Out of date doesn't seem like it would cause a problem unless by design or the upgrade step is too large of a jump.  Although I would think at that point the error message would be a little more descriptive.
    A removal and reinstall wouldn't be much worse than a migration.  Back up the database; remove SEPM (without destroying the database if possible); reinstall SEPM and connect to the existing database if available which should kick off the upgrade process; or restore the backup and manually kick off the upgrade process.  Worst case your maintenance window doubles which, in my experience, isn't that long to begin with when in-place upgrading SEPM.
    If you cannot tolerate that downtime (and I guess depending on the size of your environment) you could set up a 2nd instance of the existing version of SEPM, cluster the pair, wait or force your clients to update their connection settings to recognize the new node, tear down and replace or repair and upgrade the problematic node.  If you need to retain SEPM on the same OS at the end of this exorcise, simply fail back/remove the spare node.
            -  Hope this helps,