SharePoint security fixes released with January 2017 PU and offered through Microsoft Update

SharePoint 2007 Suite:

  • none

SharePoint 2010 Suite:

  • none

SharePoint 2013 Suite:

  • none

SharePoint 2016 Suite:

  • Microsoft SharePoint Enterprise Server 2016

See the security bulletin below for more details and KB number for the relevant fixes:

Comments (15)

  1. Scott says:

    No security Fixes for SP2010 also = no CU for SP2010 since no feature updates since end of life? Correct?

  2. James says:

    Question since the November and December PU are included in the January Secuirty update it is safe to assume we can jump to the January 2017 update correct?

    1. For which Product version?
      In November and December we did not have security fixes for SharePoint 2016 and that is the only one we have in January.
      Also be aware that security fixes are cumulative per component. So you cannot assume that a security fix in January will include the security from December or November.

  3. msekkappan says:

    Stefan, do I need to run PSConfig.exe after installing the January 2017? The patch status says “Update for Microsoft SharePoint Enterprise Server 2013 (KB3141481) 64-Bit Edition” is installed

  4. Peter says:

    Hello Stefan, is it a bug in this PU?
    The incremental crawl runs only 1m 30sec, after patching, the incremental crawler runs after psconfig 55m 🙁
    The perfomance from the SQL-Server gows down.

    1. Hi Peter,
      from what I know this has not yet been reported.
      I would recommend to open a support case with Microsoft to get this analyzed.

  5. I just installed the security fix on my SP2016-box, and after running the PSConfig-Wizard I got two errors:

    Exception: Cannot open database “sp2016_SecureStore” requested by the login. The login failed.
    Exception: Cannot open database “sp2016_BusinessDataCatalog” requested by the login. The login failed.

    Looking at the database the user executing the config-wizard doesn’t have permission. DBO of those databases is the farm-account (which I’m usually not using to log-on).

    Checking with an SP2013-box this is the same. My setup-account has no permission, just the farm-account and the services-account. So far I never had a problem. Maybe the upgrade is supposed to be executed by the timer-job, which is running as the farm-account?

    So far I’ve upgraded only using the wizard, not the commandline psconfig.exe – or do I have to run the psconfig as farm-admin? I guess I would also need to add the farm-admin to the local admin-group (which he currently is not).

    1. Hi Henning,

      that has not changed.
      See here:
      section “Setup user administrator account”


      1. Well, that is true for my setup account – with the exception to the following databases:
        – BusinessDataCatalog
        – SecureStore
        – Sync

        I installed SP2016 using the famous AutoSPInstaller … So I suppose I should grant the setup-account ShellAdmin-Access in order to successfully run the upgrade?

          1. OK, that did work – however, since (as recommended by administrative accounts) the SharePoint farm service account is not a local-admin it cannot assign shell-admin permissions. So at first I had to make the farm-admin a local admin, then start an elevated shell as farm-admin grant the setup-account shell-access and then issue the psconfig-command as the setup-account. And of course retract the farm-admin from the local admins prior to logging out of the system.

            Seems like quite som hassel – but, finally it did work – well, after running upgrade-spcontentdatabase on a couple of databases, which didn’t got upgraded properly by psconfig.

  6. laurent says:

    hello Stefan,
    i met this alert on my SharePoint 2013 Platform ” Security Update for Microsoft SharePoint Enterprise Server 2013 (KB3054813) 64-Bit Edition 15.0.4753.1000 Missing/Required”
    could you help me to fix it?
    my SharePoint informations are:
    DisplayName : Microsoft SharePoint Server 2013
    DisplayVersion : 15.0.4571.1502
    DisplayName : Language Pack for SharePoint and Project Server 2013 – French/Français
    DisplayVersion : 15.0.4571.1502

    kind regards,

    1. Hi Laurant,
      I would suggest to open a support ticket with Microsoft on this.

Skip to main content