none
Cannot install SharePoint Enterprise update due to installed Foundation updates RRS feed

  • Question

  • Hello all,

    I have been tasked with updating a couple of SharePoint Enterprise Server 2013 farms.  Not being a SharePoint expert, I have restored backups of relevant VMs (SP, SQL, AD) into a sandbox environment to make sure I have the process down before doing it on the live VMs.  During this process, I have discovered that somehow some SharePoint Foundation 2013 updates were installed a few months back (before I was involved in the process) and I am now unable to install the latest SharePoint Enterprise Server update.

    If I try to run the "Enterprise" version of the monthly update I get an error:

    "Installation of this package failed."

    However, I am able to install the "Foundation" version of the update.  I have actually installed it a couple times trying to figure out why certain components won't update (now I know why).  I even went so far as to see if I could add a new server to the farm and migrate everything to new servers, but because it sees both "Enterprise" and "Foundation" installed, I cannot add it to the farm because I cannot get both versions installed.

    I am not sure how to proceed at this point.  I could install the Foundation update, but that really only exascerbates the problem.  There are plans in the works to migrate to 2016, but I would assume that this problem will prevent that until we can get everything on only "Enterprise" again.  

    My only thought at the moment is to "migrate" from Foundation to Enterprise, and I'm not even sure that is a guarantee of fixing it. I found this TechNet article (https://social.technet.microsoft.com/wiki/contents/articles/16033.sharepoint-2013-migrate-from-sharepoint-foundation-2013-to-sharepoint-server-2013.aspx), which has several sub-links to various articles regarding upgrading/migrating SharePoint.  I just wanted to get some expert advice/suggestions before heading down that road.

    Thanks in advance.

    Eric

    Monday, April 23, 2018 9:44 AM

Answers

  • Keep in mind SharePoint VMs are not supported for online backups/snapshots.

    That being said, what update are you attempting to install? If you're installing a CU, do you have the two cab files in the same directory as the uber exe file?


    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Monday, April 23, 2018 1:37 PM
    Moderator

All replies

  • Keep in mind SharePoint VMs are not supported for online backups/snapshots.

    That being said, what update are you attempting to install? If you're installing a CU, do you have the two cab files in the same directory as the uber exe file?


    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Monday, April 23, 2018 1:37 PM
    Moderator
  • I did have them, but it seems that at least one was corrupted.  I re-downloaded them and re-copied them to the VHDX that I use for getting files "into the sandbox".  The update *seems* to be proceeding normally.  I will let it run overnight and see what happens come morning (as it will take a few hours to run).

    Thanks for the tip.

    Eric

    Monday, April 23, 2018 2:30 PM
  • Hi Mighty, 

    Have you installed SP1 for your SharePoint 2013?

    Before install the latest update, you must have Microsoft SharePoint Server 2013 Service Pack 1 installed.

    You can download SP1 from the following URL:

    https://www.microsoft.com/en-us/download/details.aspx?id=42544

    Best Regards, 

    Lisa Chen



    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, April 24, 2018 8:30 AM
    Moderator
  • Well, that was the issue.  I wish I had discovered the bad file sooner and saved myself a lot of time. :\

    Another thing that puzzles me:  even after installing the update, several items in the "Product and Patch Installation Status" section, it will show a component (e.g. Microsoft Access Services Server) and then several updates underneath it (with KB number - e.g. Update for Microsoft SharePoint Enterprise Server 2013 (KB3115174) 64-Bit Edition ).  Problem is that most of the components show an older version that what was just installed, and the updates listed beneath it are usually not current and often superseded.  How is it that the latest update doesn't update the superseded update(s), especially when it was a previous cumulative update?  Or am I misreading this list?

    It would be nice if there was a more straightforward way to get the update information

    Thanks again for the tip.

    Eric

    Tuesday, April 24, 2018 2:58 PM
  • SharePoint 2013 and previous patching was a bit complex. Not all updates superseded one another, but the updates will still be listed even if they are superseded.

    SharePoint 2016 improves this significantly.

    I have a script which may help at least get this information in a more usable state. Not sure if it will resolve your specific concern.

    https://github.com/Nauplius/SharePointProductInformation


    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Tuesday, April 24, 2018 3:06 PM
    Moderator
  • Super.  Thanks. I will check it out.

    Eric

    Tuesday, April 24, 2018 3:09 PM