Service Pack 1 for SharePoint 2013

Update:

Microsoft has discovered some problem with SharePoint 2013 Service Pack 1. So do not update your environments until further notice

We have recently uncovered an issue with the following Service Pack 1 packages that may prevent customers with Service Pack 1 from deploying future Public Updates.  As a precautionary measure we have deactivated the download pages until new packages are published.

http://support.microsoft.com/kb/2817429

http://blogs.technet.com/b/office_sustained_engineering/archive/2014/02/25/announcing-the-release-of-service-pack-1-for-office-2013-and-sharepoint-2013.aspx

Service Pack 1 (SP1) for SharePoint 2013 family of products is now available! Service Pack 1 provides fixes to improve general stability, functionality, and security in Office, SharePoint Server, and other related products.Microsoft SharePoint Server 2013 Service Pack 1 (SP1) provides the latest updates for SharePoint Server 2013. This service pack includes two kinds of fixes:

  1. Previously unreleased fixes that are included in this service pack. In addition to general product fixes, these fixes include improvements in stability, performance, and security.
  2. All the monthly security updates that were released through January 2014, and all the Cumulative Updates that were released through December 2013.

The service pack for SharePoint can be downloaded here

List of issues fixed

SharePoint2817429​Metadata is lost when documents that use a custom content type with a “Description” field are opened for editing.
SharePoint2817429​When an item is deleted, restored from recycle bin, and then deleted again, there is a primary key constraint error.
SharePoint2817429​An error occurs when files are moved between document libraries and the web time zone is behind that of the server.
SharePoint2817429​Metadata filtering at list level always lists all metadata terms.
SharePoint2817429​The hyperlink popup window drops the selected word to be linked when there is a delay of more than one second in opening the window.
SharePoint2817429​Multiple-column, SummaryLinkWebParts with a group heading style of “Separator” are rendered incorrectly.
SharePoint2817429​A hash tag that contains a full width space does not get created successfully.
SharePoint2817429​Search schema compression is now enabled by default to allow larger search schemas.
SharePoint2817429​Highlighting for FQL queries is now enabled for FQL as well as KQL.
SharePoint2817429​Opening a custom SharePoint list in datasheet view and applying multiple custom filters, where each filter has more than one condition, can result in an incomplete set of list items.
SharePoint2817429​When the “Export to Excel” button is clicked in a SharePoint document library that has the Content Type field displayed, the Content Type field does not appear in the Excel workbook.
SharePoint2817429​An error occurs after changing the “Manager” property in EditProfile.aspx page when the My Sites WebApp is not in the same farm as the UPA.
SharePoint2817429​SharePoint REST API does not return a well-defined error response for a duplicate key exception.
SharePoint2817429​Developers are unable to specify a Content Type ID when creating Content Types in the client object model.
SharePoint2817429​On list views in SharePoint sites, the Connect to Outlook button in the ribbon may be erroneously disabled.
SharePoint2817429​In some non-English languages of SharePoint, the text displayed in the callout UI for a document or list item, describing who last edited the item, may not be grammatically correct.
SharePoint2817429​Copy and Paste in a datasheet does not work correctly with Internet Explorer 11.
SharePoint2817429​Pages do not render in Safari for iPad when private browsing mode is used.
SharePoint2817429​When editing rich text fields in SharePoint, if the editing session exceeds 30 minutes, the edits may not be saved.
SharePoint2817429​An error that says “SCRIPT12004: An internal error occurred in the Microsoft Internet extensions” may occur intermittently when users visit their SkyDrive Pro or other pages on their personal site.
SharePoint2817429​InfoPath may crash when a form that points to a SharePoint list, with a lookup to another SharePoint list, is opened.
SharePoint2817429​An InfoPath form with extended characters in its name fails to open.
SharePoint2817429​An error that says “Security Validation for the form has timed out” may occur when an InfoPath form is digitally signed and hosted in a SharePoint site collection that uses the SharePoint version 2010 user experience.
SharePoint2817429​“Show document icon” remains unchecked and the document icon does not show in Edit Properties for a list item.
SharePoint2817429​A “Failed tagging this page” error occurs when the “I like it” button is clicked.
SharePoint2817429​The wrong term is removed when manually editing a multi-valued taxonomy field.
SharePoint2817429​When tagging list items using a language that is different from the term store default language, suggestions for labels are offered in multiple languages. The suggestions appear confusing because both language suggestions are listed without any identification of the language.
SharePoint2817429​An error that says “There was an error processing this request” may appear when editing the user profile.
SharePoint2817429​Times are missing from Date/Time results in certain filtered list web service calls.
SharePoint2817429​Minimal and no metadata are now enabled as supported JSON formats.
SharePoint2817429​Actions4 schema workflow actions can’t be deployed to SharePoint.
SharePoint2817429​Using Client Object Model, Stream.Seek() to seek to a particular position doesn’t seek at the proper offset.
SharePoint2817429​Refreshing a workflow status page generates the following error: “System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.”
SharePoint2817429​Setting custom, non-English outcomes in web pages on tasks in a workflow fails to set the value.
SharePoint2817429​Configurations of SharePoint using Azure Hybrid mode and Workflow Manager together can cause workflow callbacks to fail.
SharePoint2817429​Workflow task processes on wiki pages won’t start.
SharePoint2817429​Workflows won’t wait for changes to content approval status fields.
SharePoint2817429​E-mails generated by workflow cannot be disabled for approvals in SharePoint workflows.
SharePoint2817429​Workflows may fail to send an e-mail or send too many e-mails.
SharePoint2817429​Association variables do not update correctly for auto-start workflows.
SharePoint2817429​A KeyNotFoundException error may occur in a workflow when the associated task list uses unique permissions.
SharePoint2817429​Incomplete tasks are deleted when workflow task activities complete.
SharePoint2817429​Task activity is suspended when the task is completed using app-only credentials.
SharePoint2817429​An error that says “This task could not be updated at this time” occurs when trying to complete a workflow task using the “Open this task” button in Outlook.
SharePoint2817429​A workflow doesn’t respond properly when waiting for changes in specific types of list columns, such as Boolean, Date Time, and User.

Office 2010 and SharePoint 2010 Service Pack 2 now available

Office and SharePoint 2010 Service Pack 2 (SP2) is now available!. The SP2 release improves the compatibility of the Office and SharePoint 2010 products with Windows 8, Internet Explorer 10, Office 2013, and SharePoint 2013. It also addresses several security, stability, and performance issues.

As of today, all of the SP2 updates are available from the Download Center at the links listed below as well as from Microsoft Update as a manual download. After a 90-day period, SP2 will be offered as an automatic update through Microsoft Update.

  1. Service Pack 2 also includes a roll-up of all Cumulative Updates through April 2013, and all Public Updates through May 2013. The list below is specific to changes shipping for the first time in SP2.
  2. Text for some list items describes a problem now fixed by SP2, while other items describe both the problem and the new behavior after installing SP2. Despite variations in phrasing, SP2 fixes all of the issues listed.
  3. SP2 also contains additional changes which are less visible, but improve various aspects of the product. This includes reducing crashes, improving security, and fixing other issues too specific to include in this list.
The issues fixed specifically in the service pack are listed here

Source:

SharePoint database is currently running in backwards compatible mode

The other day I saw an error on my SharePoint environment stating the following error
“SharePoint object [SPContentDatabase Name=SharePoint_AdminContent_c8de0fec-7405-48f2-9fef-ed15ae4b1125] is currently running in backwards compatible mode. Please fully upgrade it to ensure optimal performance from this object” So, what exactly is the message all about, let us understand. The “Backward compatibility Mode” has been newly introduced in SharePoint 2010.This is a new feature in SharePoint 2010 which allows you to defer the database upgrade even though the binaries on your server are upgraded. So what does that mean Following scenario depicts how you could enter a “Backward compatibility Mode” (either planned or accidental as in my case)

  1. You install a service pack in your SharePoint environment successfully
  2. But you do not run the “SharePoint Configuration Wizard” which is responsible to update the database or do not run psconfig (for advanced users)

The above steps leave your databases in a “backward compatibility mode”. i.e. When the database upgrade is deferred, the databases enter the “backwards compatibility mode” Pros:

  1. Defer update of database to later date/time to avoid immediate downtime and support high availability for users (The accepted duration of running in this mode would be few days or maybe a week but not more than that)

Cons:

  1. Running for long durations in this mode could lead to undesired results

Catch: This mode works on a baseline as to what should be the minimum version of database you should be running (if you choose to upgrade the database at a later date). The backward compatibility mode is supposed to be re-based lined with each Service Pack releases, i.e. Service Packs should introduce a compatibility boundary. A compatibly boundary would mean that after a particular Service Pack deployment, we would not be able to upgrade binaries on the server and defer database upgrade. The supported baseline is N-1 range of binaries on servers to database backwards compatibility where N equals to Service Pack build. Example:

  1. You install SP1 for SharePoint but do not run “SharePoint Configuration Wizard” and hence you enter “backward compatibility mode”
  2. Should you need to install future SP (e.g. SP2) (N) then you must be at least running the database version SP1(N-1)

Installing SharePoint 2010 SP1 and June CU

It is recommend to first apply SP1 to your SharePoint environment because it resets the baseline for your entire SharePoint environment, and prepares your environment for future releases such as the June CU. The recommended order in which you should apply SharePoint Foundation vs. SharePoint Server Updates. As Per the guidance from the SharePoint team, when applying SP1 or the CU it is recommended to apply the Foundation packages before applying the Server packages. SharePoint Foundation 2010:

  1. Download SharePoint Foundation 2010 SP1
  2. Download June 2011 CU for SharePoint Foundation 2010
  3. Install SharePoint Foundation 2010 SP1
  4. Reboot Server
  5. Once the server has rebooted, start SharePoint Configuration Wizard and complete the process.
  6. Upon completion you should be able to open Central Administration window.
  7. Verify Upgrade Success: After installing SP1, the version of the content databases will be 14.0.6029.1000

You’ve got a new baseline for future CU’s

  1. Install June 2011 CU for SharePoint Foundation 2010
  2. Reboot Server
  3. Once the server has rebooted, start SharePoint Configuration Wizard and complete the process.
  4. Upon completion you should be able to open Central Administration window.
  5. Verify Upgrade Success: After installing the June 2011 CU, the version of the content databases will be 14.0.6106.5000 / 14.0.6106.5002

SharePoint Server Standard/Enterprise 2010:

  1. Download SharePoint Foundation 2010 SP1
  2. Download SharePoint Server SP1
  3. Download June 2011 CU for SharePoint Foundation 2010
  4. Download June 2011 CU for SharePoint Server 2010
  5. Install SharePoint Foundation 2010 SP1
  6. Install SharePoint Server SP1.
  7. Reboot Server
  8. Once the server has rebooted, start SharePoint Configuration Wizard and complete the process.
  9. Upon completion you should be able to open Central Administration window.
  10. Verify Upgrade Success: After installing SP1, the version of the content databases will be 14.0.6029.1000

You’ve got a new baseline for future CU’s

  1. Install June 2011 CU for SharePoint Foundation 2010
  2. Install June 2011 CU for SharePoint Server 2010
  3. Reboot Server
  4. Once the server has rebooted, start SharePoint Configuration Wizard and complete the process.
  5. Upon completion you should be able to open Central Administration window.
  6. Verify Upgrade Success: After installing the June 2011 CU, the version of the content databases will be 14.0.6106.5000 / 14.0.6106.5002

SharePoint Server 2010 SP1 Released

Microsoft SharePoint Server 2010 Service Pack 1 (SP1) provides the latest updates for SharePoint Server 2010.

Overview of SharePoint Server 2010 SP1 improvements

Specifically, these are the key areas of improvement in SP1:

  • Improved support for Internet Explorer 9.
  • Recycle bin: Lets you restore a site collection or a web that was deleted.
  • Remote Backup Systems (RBS) and shallow copy can decrease downtime and increase efficiency by moving pointers to databases instead of moving databases.
  • You can see which folders are taking up valuable space with the improved Storage Management feature in site settings.
  • Support for Microsoft SQL Server 2011.
  • A more robust Search Host Distribution service that improves error recovery and performance during the search crawl.
  • Adds backup and restore functionality to recover deleted site collections and webs.

Download:

 
   
: