Blog Links
Socials
Related Posts
SP1 is now available for SharePoint Server 2013, Project Server 2013, Project 2013, and SharePoint Designer 2013!
Build number as seen in central admin after installation: 15.0.4569.1000
[2nd update, 2014-04-22]
The updated version of Service Pack 1 has been released! Note that the KB articles are now different! See table below!
Please see all details here: http://blogs.technet.com/b/stefan_gossner/archive/2014/04/22/sp1-for-sharepoint-2013-has-been-rereleased.aspxOther References: official announcement in Bill Baers blog post.
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.
[/update 2014-04-22]
---------------------------------------------------------------------------------------------------------------------------------------------------
[update 2014-04-08]
-- Due to a potential issue with SP1 that prevents deployment of future PU/CU's, the download was disabled!
-- Please read more here: http://blogs.technet.com/b/wbaer/archive/2014/04/08/service-pack-for-sharepoint-server-2013-1-recalled.aspx
-- I'll post an update as soon as it is newly released.
[/update 2014-04-08]
NOTE! The March PU Is not required prior to install SP1 on top of RTM version!
(see also the Sustained Engineering blog post)
The updates are available from the Microsoft Download Center today, as well as from Microsoft Update and the Windows Server Update Services (WSUS) catalog. After a 30-day period, SP1 will begin releasing as an automatic update through Microsoft Update. Visit these KB articles for more information on the SP1 updates for the MSI versions and how to get them.
SharePoint Server 2013 SP1 *Re-released Service Pack: KB 2880552
2817429new KB 2880552
Office Web Apps Server 2013 SP1Known ISSUE: Office Web Apps 2013 in April PU and SharePoint 2013 SP1
2850035
2880554
2880555
Customers who have an Office 365 subscription are always kept up to date and will get the SP1 changes automatically in their next regular update.
SP1 for Exchange Server 2013 is also releasing today. Visit the Exchange team blog to learn more about it.
* Note! after installing the SharePoint Foundation SP1 you should also install on top the hotfix from KB2760625 which solves a problem with search, please see more in the KB as well as the blog of my colleague, Stefan Gossner.Please download and install the new, re-released Service packs! See more details here: http://blogs.technet.com/b/stefan_gossner/archive/2014/04/22/sp1-for-sharepoint-2013-has-been-rereleased.aspx- The KB articles for the re-released Service Packs are different from the recalled Service Pack! See updated table above!
What’s new in SP1?
SP1 provides fixes to improve general stability, functionality, and security in Office, SharePoint Server, and related products. Among the functionality improvements and changes are the following:
SP1 includes all the Public Updates (PU) and Cumulative Updates (CU) that have been released since the 2013 family of products first became available, up to the December 2013 CU and January 2014 PU.Issues Fixed by Service Pack 1 (SP1) in Office and SharePoint 2013list of SP1 fixes is available for download
Support for Windows Server 2012:
Language Packs:
Regarding the installation ensure to follow all guidelines on the following page: Software updates overview for SharePoint 2013
Note! As usual, you must run the PSConfig Wizard after installation to finalize the update!
Related Posts:
Hi, Steve, thanks a lot for the great news. It seems we encountered a strange issue after applying the SP1 update. All our 3rd party software service accounts lost the dbo permission on the SharePoint databases and can no longer work unless the permission is manually set again. Is this the expected behavior? any insights would be greatly appreciated!
@George White:Hello and thanks for the heads-up, currently we are not aware of this specific issue and you should open a support case to follow up if this is a regression we might have overseen.I tested myself the Server SP1 on a standard Farm setup on either Straight RTM as well as on a patched Farm at Dec. 13 CU, both farm's went through fine and no issues were seen, so I think, this is really something we should investigate by a Support case since 3rd party software and hence service accounts are quiet common. So I'd really recommend to raise a case if you find this critical for your deployment.HtH, cheers, Steve