SP1 for SharePoint 2013 has been rereleased

- - 115 Comments

The updated version of Service Pack 1 has been released today!

Refer to the information below to acquire the updated Service Pack for your product:

NOTE The KB articles for the re-released Service Pack is different from the recalled Service Pack.

  • KB 2880551 – SharePoint Foundation 2013 SP1
  • KB 2880552 – SharePoint Server 2013 SP1
  • KB 2880553 – Project Server 2013 SP1
  • KB 2880554 – SharePoint Server Language Pack
  • KB 2880555 – SharePoint Foundation Language Pack
  • KB 2880558 – Office Web Apps Server 2013 SP1

Download links for updated SP1:

  

Customers with Service Pack 1 Deployed

For customers who have previously deployed Service Pack 1, download the updated Service Pack 1 and install over the existing Service Pack 1 running PSConfig or PSConfigUI immediately following.

 

Customers without Service Pack 1

For customers without Service Pack 1 deployed, download the updated Service Pack 1 package and deploy as per the KB documentation.

 

MSDN/VLSC/MPN ISO

There is no update to the integrated ISO ("slipstream") from MSDN, VLSC and MPN as it was not affected by the issue.

Reference

see official announcement in Bill Baers blog post.

115 Comments


  1. The updated version of Service Pack 1 has been released today! Refer to the information below to acquire

    Reply

  2. Re-Release of SP1 is available! My colleague Stefan was the first one, so please check his blog post

    Reply

  3. Después de los problemas que ha ocasionado el Service Pack (SP) 1 de SharePoint 2013, Microsoft acaba

    Reply

  4. La nouvelle circule depuis quelques heures sur les réseaux sociaux et autres média de communications

    Reply

  6. SP1 is now available for SharePoint Server 2013, Project Server 2013, Project 2013, and SharePoint Designer

    Reply

  7. Hi Stefan, what about Service Pack 1 for Language Packs for Microsoft Office Web Apps Server?
    Steffen

    Reply

  8. Hi Steffen, installing SP1 for Microsoft Office Web Apps Server seems to contain patches for all language packs as well. You can see that at the end of the binary which is not language specific (e.g. en-us but gbl which means global)

    Reply

  9. Hello,

    Do I need to reinstall all of the SP1 LPs for SharePoint server as well. I have previously install SharePoint SP1 + LPs SP1

    Reply

  11. Hi George,
    yes you should reinstall also SP1 for all LP.
    Cheers,
    Stefan

    Reply

  13. Buenas, Ya están disponibles las nuevas versiones del Service Pack 1 para SharePoint server 2013, Project

    Reply

  14. Thanks Stephan for this news. About SharePoint Foundation SP1, is it a new SP1 including the fix for search web part (March 2014 Public Update (PU) ) or do we have to appy this PU ?
    Regards

    EtienneL

    Reply

  15. Hi Etiennel,
    this fix is included in the re-released SP1. You will find a note at the beginning of the Foundation SP1 KB article.
    Cheers Stefan

    Reply

  16. Hi Stefan, what would be the build number of SP1 ?
    The SP1 that was retracted from the download site was: 15.0.4569.1506

    Thanks.

    Reply

  18. Hi,
    The initial release of SharePoint Foundation 2013 slipstream ISO was affected by search issue.
    Now, "There is no update to the integrated ISO ("slipstream") from MSDN, VLSC and MPN as it was not affected by the issue." Some information is incorrect?

    What is correct/best path to install new clean SharePoint Foundation 2013 farm with SP1 or Windows 2012 or 2012 R2?

    Install Windows 2012 Server + SharePoint Foundation 2013 (http://www.microsoft.com/en-us/download/details.aspx?id=35488) + LP + (maybe also PU1) + new SharePoint SP1 (http://support.microsoft.com/kb/2880551) + new LP SP1 + psconfig.

    Or,
    install Windows 2012 R2 Server + SharePoint Foundation 2013 with SP1 (http://www.microsoft.com/en-us/download/details.aspx?id=42039) + LP with SP1 + KB2760625 (http://support.microsoft.com/kb/2760625) + psconfig.

    Or something else?

    Thank you very much,
    Josef

    Reply

  19. I'm assuming that the Project Server 2013 SP1 INCLUDES the SharePoint 2013 SP1 files, correct?

    Reply

  20. Hi Stefan
    It took me hours to install SP1 & LP SP1 on the Farm. I can't belive I have to do this again! Is reinstalling really the only way to get rid of the Bug?
    Thanks

    Reply

  21. Hi Josef,
    the slipstream was NOT affected by the issue that caused the re-release of SP1 (the fact that future fixes could not be installed on servers patched with SP1).
    the slipstream install WAS affected by the search issue.
    The re-released SP1 fixes both issues but only exists as update and not as slipstream.

    So you need to install the separate fix for the search issue on slipstream but not on the re-released SP1.

    Hope this clarifies your question.

    Cheers,
    Stefan

    Reply

  22. Hi Andrea,
    unfortunatelly that is the only way to fix the installer problem.
    Cheers,
    Stefan

    Reply

  23. Hi Kathryn,
    sorry this is not correct. Project Server SP1 is very small and contains only the Project Server related updates.
    You need to install as well SharePoint Server SP1 and Project Server SP1.
    Cheers,
    Stefan

    Reply

  25. @Daniel
    Thanks for the Link. Looks promising…

    Reply

  26. Hi Elan,
    sorry for the delay. The version of rereleased SP1 is 15.0.4571.1502

    Reply

  27. Stefan, per Bill Baer, the SP 2013 August 2014 CU officially adds support for SQL Server 2014. But you said the August CU had been scaled back due to issues in SP1. Was the SQL 2014 support one of the things that was affected? I'm about to build a new farm so I'd like to know if I can use SQL 2014.

    Reply

  28. Hi Greg,

    I guess that you mean April CU.
    April CU for SharePoint 2013 has not been released – so SQL 2014 will be supported with the next CU.

    Cheers,
    Stefan

    Reply

  29. Stefan, can you clarify or link to "the search issue"? I don't see any info about search being effected in the SP1 changes document from Support.

    Reply

  30. Hi Matthew,
    please check the top section of this article:
    http://support.microsoft.com/kb/2880551/en-us

    In addition, this service pack also fixes the following issue:

    The Search box is missing after installing the public update such as MS13-100 (KB 2850058). You may receive the “Sorry something went wrong” error message when you try to access the Search Center.

    Reply

  31. Stefan The integrated ISO is not affected. Does that mean that there is no need to install the new SP1 over the existing SP1 and buildnumbers are equal?

    Reply

  32. Hi Boevink,

    there is no need to install the new SP1 over the existing SP1 – but build numbers are not equal.

    Cheers,
    Stefan

    Reply

  33. Hi Stefan

    Regarding the April CU that adds support for SQL Server 2014 – any indication when this CU will be available?

    We had planned to start testing SharePoint 2013 with SQL Server 2014 this month but have not thus far been able to due to the delay with the April CU.

    I'd like to plan this work in my team so any indication would be useful.

    Thanks

    Reply

  34. Hi Bob,

    we don’t have information if there will be a fix for this before June CU.
    Latest with June CU Support for SQL Server 2014 will be provided.

    Cheers,
    Stefan

    Reply

  35. Thanks Stefan.

    My curiosity got the best of me so I went ahead and tried SharePoint 2013 SP1 with SQL Server 2014.

    Everything seems to be working perfectly. My basic testing has not found any issues thus far.

    Is there anything in particular that you know is currently a compatibility issue between SharePoint 2013 and SQL Server 2014, and that won't be fixed until the June CU?

    Thanks
    Bob

    Reply

  36. Hi Bob,

    I’m not aware of any issues but it is not supported. The reason is that tests with SQL 2014 have been done on the April CU code base – not on any earlier code base.
    So if any issues arise you cannot open a support case unless you are on at least the tested code base.

    Cheers,
    Stefan

    Reply

  37. You're a legend for consistently replying promptly to your blog readers Stefan – thank you.

    Look forward to the next CU for SharePoint 2013.

    Bob

    Reply

  38. Hi Stefan,

    If I install KB2880558, do I need to install anything else? I mean, the Office Web Apps Server SP1 includes the rest of SP1's?

    By the way, I have the first released SP1 installed in my farm.

    Thank you,

    José

    Reply

  39. Hi Jose,
    Office Web Apps Server SP1 does NOT include SharePoint Server SP1.
    Cheers,
    Stefan

    Reply

  40. Pingback from April 2013 CU for SharePoint 2013 has finally been released – Stefan Go??ner – Site Home – TechNet Blogs

    Reply

  41. Pingback from April 2014 CU for SharePoint 2013 has finally been released – Stefan Go??ner – Site Home – TechNet Blogs

    Reply

  42. Pingback from April 2014 CU for SharePoint 2013 has finally been released – Stefan Go??ner – Site Home – TechNet Blogs

    Reply

  43. Pingback from April 2014 CU for SharePoint 2013 has finally been released – Stefan Go??ner – Site Home – TechNet Blogs

    Reply

  44. Pingback from April 2014 CU for SharePoint 2013 has finally been released – Stefan Go??ner – Site Home – TechNet Blogs

    Reply

  45. Pingback from April 2014 CU for SharePoint 2013 has finally been released – Stefan Go??ner – Site Home – TechNet Blogs

    Reply

  46. Pingback from April 2014 CU for SharePoint 2013 has finally been released – Stefan Go??ner – Site Home – TechNet Blogs

    Reply

  47. Pingback from April 2014 CU for SharePoint 2013 has finally been released – Stefan Go??ner – Site Home – TechNet Blogs

    Reply

  48. Be aware that all Updates for SharePoint 2013 require March 2013 PU for SharePoint 2013 to be installed

    Reply

  49. Hi Stefan: I installed Project Server SP1 (KB2880553) over all the servers in my farm already having Project Server SP1. Trying to configure with SharePoint Configuration Wizard and getting error Microsoft Project Server 2013 (15.0.4571.1502)
    Missing on ServerName
    Service Pack 1 for Microsoft Project Server 2013 (KB2880553) 64-Bit Edition (15.0.4571.1502)
    Missing on ServerName. The Central Administartion is also not running. When trying to install the SP1 again it gives message that it is already installed. What is to be done?

    Reply

  50. Hi Gops,
    sorry but its not possible to determine what went wrong using this information.
    I would recommend to open a support case.
    Cheers,
    Stefan

    Reply

  51. Hi,
    I am trying to install the new SharePoint SP1 update on a farm that I already installed the old update on. I have 2 wfes and 2 app servers. The problem is sharepoint products config has been running non stop for 24 hours. Am I missing something? Is anyone getting
    this issue>

    Reply

  52. Hi Stefan: I reconfigured my Project server 2013 farm with SP1. Now I will be applying the updated SP1 installed Project Server SP1 (KB2880553) over all the servers in my farm . Do I have to apply updated SharePoint Service 2013 Pack KB2880552 and KB2880551
    separately or SP1 (KB2880553) contains updates for SharePoint 2013 also (as before). Can you also give the order of applying, if all the three needs to be applied separately.

    Thanks.

    Reply

  53. Project Server SP1 does not include SharePoint SP1. Neither the first release nor the re-released one.

    Reply

  54. Hi Stefan,
    We have the follow scenario:

    We used a Slipstreamed version of SP2013 including the March PU. Then we (added) slipstreamed this version with the SP1, that was available one day after it was released. So we have a SP2013RTM+marchPU+SP1 as slipstream version. Is this the correct way as we
    already installed a Farm with that.

    Reply

  56. So we have to install and set up our whole farm again. Because your link states specifically RTM not march PU
    "A couple of people already tried to create their own slipstream version using RTM and SP1"

    And we already had that march PU embedded in the slipstream which has the new package layout. And on top of that SP1. So RTM+PU+SP1 or is that also wrong?

    Thnx for the quick reply btw!

    Reply

  57. Hi Sjimmie,

    I’m not an official source for such a statement. Please open a support case to allow us to contact the PG to double check if your specific scenario is supported or not.
    The statement we got is to use the official slipstream builds.

    Cheers,
    Stefan

    Reply

  58. Dear Stefan,
    After I installed the package & run the Configuration Wizards, I got the error as below. Can you please advise the solution ?

    Timestamp Process TID Area Category EventID Level Message Correlation
    05/29/2014 17:39:01.03 OWSTIMER (0x16F4) 0x1824 SharePoint Foundation Upgrade SPContentDatabaseSequence ajxkh ERROR The feature with Id c4cb1d70-9679-404e-8822-284f6b95b75a is referenced in the database [WSS_Content_SharePoint2013_UAT_6009], but is not installed
    on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary. 4898959c-a99c-10eb-aa18-7f2dbcacf696

    05/29/2014 17:43:23.86 OWSTIMER (0x16F4) 0x1824 SharePoint Foundation Upgrade SPUpgradeSession aj0ur ERROR Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors. Review the upgrade log
    file located in C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15LOGSUpgrade-20140529-173135-373.log. The number of errors and warnings is listed at the end of the upgrade log file. at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
    at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd() at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId) 4898959c-a99c-10eb-aa18-7f2dbcacf696

    Reply

  59. Hi Anthony,
    the guid in the error message "c4cb1d70-9679-404e-8822-284f6b95b75a" lists a custom feaure. It is not a feature coming with SharePoint.

    it seems that feature – although referenced in a content db – is not installed on the farm.

    You need to identify which custom feature this Guid belongs to and install it on the farm.

    Cheers,
    Stefan

    Reply

  60. Hi Stefan, thanks for your response.

    I found a solution for that issue : before installing the SP1 , we should run Features Admin to remove all corrupted or error features in the SharePoint farm.

    Tool: http://featureadmin.codeplex.com/

    Cheers,
    Anthony.

    Reply

  62. Hola
    Están disponibles de nuevo los paquetes de SP1 para SP 2013.
    Por favor os refiero al

    Reply

  64. Hi Huu,

    the method in this article has not officially been tested but we know that many customers use it successfully and till now we haven’t heard back about any issues.

    Cheers,
    Stefan

    Reply

  65. Pingback from El camino de un ITPro – Actualizaci??n Acumulativa (CU) de Junio para Sharepoint 2013 ya disponible.

    Reply

  66. Pingback from June 2014 CU for SharePoint 2013 has been released – Stefan Go??ner – Site Home – TechNet Blogs

    Reply

  67. Be aware that all Updates for SharePoint 2013 require March 2013 PU for SharePoint 2013 to be installed

    Reply

  68. Pingback from SharePoint 2013 June 2014 CU

    Reply

  69. We have our SharePoint farm patched to SP1. We have now integrated Project Server into the farm. Can I just install the SP1 package (KB2881062) for Project Server to catch it up. Before it was stated that the March CU had to be installed before any other
    updates. I'm guessing that doesn't apply once SP1 was released but just thought I'd double check.

    Reply

  70. Hi Jen,
    you need to install SP1 for SharePoint and SP1 for Project server. The project server SP1 does not include SharePoint SP1.
    You are right: March CU is not required to install SP1 and also not for future CUs after SP1 has been installed.
    Cheers,
    Stefan

    Reply

  71. Hi Stephen,

    The earlier SP1 build version was 15.0.4569.1000. After installing the re-released version of SP1 will the build version change?

    Regards,
    Savio

    Reply

  72. Hi Savio,
    you should see a different version in Control Panel.
    Cheers,
    Stefan

    Reply

  73. You are reading right, we have the first monthly cumulative update package for SharePoint Server 2013

    Reply

  74. Hi Stefan,
    as far as you know, is it normal that Arabic has not been released in SP1 as Language Pack ?!?

    Reply

  75. Hi Matteo,
    no that is not expected. Not sure why it is not avail.
    As a workaround you can uninstall the language pack and install the language pack with SP1 included from the following location:

    SharePoint server:
    http://download.microsoft.com/download/8/2/3/82363272-CF71-453B-9F35-1082CA98EA49/ServerLanguagePack_x64_ar-sa.img

    SharePoint foundation:
    http://download.microsoft.com/download/6/7/9/6794C7FF-FD6F-4BDE-B5FD-119447CD0F30/spf_lpk_SP1_x64_ar-sa.img

    Cheers,
    Stefan

    Reply

  76. Hi Stefan,
    just to let you know, i did a double check and the Arabic Language Pack in SP1 is present only on MSDN.

    Funny MS 🙂

    Thanks
    MZ

    Reply

  77. Starting with the July 2014 CU, the release cycle is now every month rather than the Bi-monthly cycle

    Reply

  78. Our SharePoint product group released the next monthly cumulative updates. This month we will have the

    Reply

  79. Hi Stefan
    What is order of sequence to install all the service packs ( SharePoint Server 2013 Service Pack 1 ,SharePoint Server 2013 Language Pack Service Pack 1,Office Web Apps Server 2013 Service Pack 1,Project Server 2013 Service Pack 1)

    Reply

  80. Hi Subhash,
    there is no specific sequence.
    Cheers,
    Stefan

    Reply

  81. Microsoft acaba de liberar las actualizaciones acumuladas de Octubre de 2014 tanto para SharePoint 2010

    Reply

  82. Our SharePoint product group released the next monthly cumulative updates. This month we will have the

    Reply

  83. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  84. Since July 2014 CU, the release cycle is now every month rather than the Bi-monthly cycle. NOTE! All

    Reply

  85. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  86. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  87. I was tried to install sharepoint server 2013 on windows 2012 R2 but everytime i’m getting error at application server role and let me know how to install appfabric server

    Reply

  88. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  89. Hi Stefan,
    I am installing SharePoint 2013 SP1 and then Project Server 2013 SP1,
    Do I still needed to install-other CU which released in between- Or only recent most CU ?
    Please suggest

    Reply

  91. Helo,

    I am getting ready to patch a SP 2013 farm. The current version installed is 15.0.4569.1506. I don't believe there have been any security patches applied to the farm since the SP1 install in August of 2014. I know the patches are listed as Cumulative Updates,
    CU, however, can I run the latest CU patch from April 2015 and have all security updates installed?

    Thank you very much for your time.

    Reply

  92. Hi TD,
    in general: yes. But you have to install the rereleased SP1 before being able to apply April 2015 CU.
    Cheers,
    Stefan

    Reply

  93. So the re-released SP1 is not 15.0.4569.1506?

    Reply

  94. I found the re-release version 15.0.4571.1502, thank you for your assistance. So 1 more question: Do all packs (Foundation, server, language, project server, web apps) need to be installed then psconfig run? Thanks again.

    Reply

  96. This Month CU has been released with a full server packages, a.k.a. "Uber Packages" – so this

    Reply

  97. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  98. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  99. The product group released the July 2015 Cumulative Update for the SharePoint 2013 product family.

    Reply

  100. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  101. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  102. The product group released the August 2015 Cumulative Update for the SharePoint 2013 product family.

    Reply

  103. Hi Stefan GoBner,

    I have already installed kb2767999 on sharepoint, is it possible to installe SP1 on the March 2013 Public Update?

    Cheers,
    OGU

    Reply

  104. Hi OGU,
    sure.
    Cheers,
    Stefan

    Reply

  105. Update 9/17/2015: The issue has been fixed. See Solution for details The Problem The August 2015 Cumulative

    Reply

    1. Hi Frederik,
      that version includes SP1. No need to install SP1 on top of this.
      Cheers,
      Stefan

      Reply

  107. Is SP1 still available? I can make it to the Download page from several articles, but when I click the red download button it sits for a while and comes back with a “We’re Sorry – We can’t find the page you’re looking for” error. This is for the re-release, KB2880552.

    Reply

    1. Just tested: works for me.
      Can you try again?

      Reply

      1. Had a co-worker try with IE11 and it worked. Apparently the Download Center doesn’t like older versions of IE these days.

        Reply

  108. Hi Stefan,
    I will be adding a a new WFE server to an existing SP farm. My question is in regards to issues while installing SharePoint 2013 with windows server 2012 R2.
    My Plan:
    1) Install the pre-requisites on the new server with OS windows server 2012 R2.
    2) Install SharePoint server 2013 RTM on the new server.
    3) Then install SharePoint server 2013 SP1 on that server
    4) Then install February 2016 CU for SharePoint server 2013 on that server.
    5) Then execute PSConfig on that server to connect that server to the existing farm.
    My question to you is that is the above approach correct (install RTM then separately install SP1)? OR is it necessary to Install SharePoint server 2013 with embedded SP1 on server with OS windows server 2012 R2 and then processed with necessary CU? Please assist. Awaiting your reply. Thanks.

    Reply

    1. Hi Albi,
      you Need to install the slipstream Version of SharePoint 2013 with SP1 as RTM does not install on Windows Server 2012 R2.
      Cheers,
      Stefan

      Reply

      1. Thanks for your quick reply 🙂

        Reply

  110. We are trying to install sharepoint server 2013 with SP1 and are getting an error:
    microsoft sharepoint server 2013 encountered an error during setup

    I was wondering if i have the correct steamed SP2013 SP1 — version 15.0.4569.1506
    Prereqs have been installed and the roles/features.

    Problem signature:
    Problem Event Name: OfficeClassicSetup
    SETUP EXE VERSION: 15.0.4454.1000
    SETUP DLL NAME: SVRSETUP.DLL
    SETUP DLL VERSION: 15.0.4569.1503
    ERROR CODE: 1603
    MSI HRESULT: Unspecified
    ERROR DETAILS: FC73469E
    FIRST ERROR CODE: 1603
    OS Version: 6.3.9600.2.0.0.272.7
    Locale ID: 1031

    Any clues where to look next? I have searched above and beyond with bunch of offered fixes for the bootstrapper but nothing makes a difference.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.