January 2019 Cumulative Update is now available for SharePoint Server 2019

Microsoft has released a new Cumulative Update Pack (CU) for SharePoint Server 2019. This is the 3rd CU released since the product was made generally available last year. Cumulative update provides fixes and enhancements for the product which is a great benefit for any organization. However, it’s always recommended to try the update in a dedicated environment before installing them in production farms.

Important: Its mandatory to install both (Language Independent and language Dependent) packages to to fully patch a SharePoint Server environment. This is because, each SharePoint installation includes Language Dependent and Independent components.

The KB article for January 2019 CU will be available at the following Location in a couple of hours:

  • KB 4461634 – January 2019 Update for SharePoint Server 2019 (language independent) – This is also a security update!
  • KB 4461514 – January 2019 Update for SharePoint Server 2019 (language dependent)
  • KB 4461633 – January 2019 Update for Office Online Server 2019 – This is also a security update!

The download for January 2019 CU is available through the following link:

After installing the CUs you must run the SharePoint 2019 Products Configuration Wizard on each machine in the farm and restart them to effect the changes. If you prefer to run the command line version psconfig.exe you better have a look here for the appropriate options.

SharePoint 2019 January 2019 CU Build Numbers are: Your farm should show these numbers after successful application of the update, so ensure the numbers are reflected.

Language independent fix: 16.0.10340.12101
Language dependent fix: 16.0.10340.12100


May 2014 Cumulative has been Released for SharePoint 2013

Microsoft has recently announced the May 2014 Cumulative Package for SharePoint 2013 Foundation | Server under the Build No of 15.0.4605.1004 (Version No).

Download the Packages here – http://technet.microsoft.com/en-us/sharepoint/jj891062.aspx


  1. Before you apply the Cumulative in Production Environments, test the same in a Staging Environment thoroughly.
  2. Consider to apply this only if you are getting the mentioned issues below because it doesn’t deliver any extra benefits for you except the mentioned fixes. 


It is compulsory to have March 2013 Public Update Installed Prior to this Installation. Your farm Should have been updated with the same. Download March 2013 CU here – http://support.microsoft.com/kb/2767999 

List of Issues Fixed by this package are as below:

  1. When SharePoint Server 2013 claims the provider returns no matches, the people picker still displays a suggestion from the user information list.
  2. When you create a site by using a custom site template, the composed looks list is empty.
  3. When you view the slides in picture library, pictures may not display if the file name contains complex characters such as multibyte characters.
  4. When you create a site from a saved template that contains an AlternateCSSUrl property, the AlternateHeaderUrl value is set to the AlternateCSSUrl value incorrectly.
  5. When you add a link to the reusable HTML field in a reusable content item, the link does not work as expected.
  6. You cannot send alerts to a security group instead of a user.
  7. When you try to upload a file that exists and is checked out to a SharePoint Server 2013 document library, you receive an error message that displays the logon name instead of the display name.
  8. When you use some reusable content in a variations context, the reusable content is displayed incorrectly if the labels are in certain languages.
  9. When you change the fallback language on a SharePoint Server 2013 server, you experience high CPU usage on the server.
  10. When you configure Forms-Based Authentication (FBA) with active directory as back end for a SharePoint Server farm, the "Everyone" view on the Newsfeed page displays an error.
  11. When you view a non-published page anonymously, you receive an unexpected error.
  12. When you try to import user properties from business data connectivity (BDC) and activity directory (AD) at the same time, the time zone is not updated.
  13. When you experience an error during ping checks in the health check of Office Web App Server (WAC), all future checks fail until you restart the process.
  14. When you select a Web Part on a publishing page, the ribbon context is changed incorrectly.
  15. Assume that you create a list workflow on list A that creates an item on list B. Then, you create another list workflow on list B. When you create an item on list A and start the workflow for the list, list B is not triggered as expected.
  16. When you use SharePoint Designer 2013 to deploy a workflow that contains an activity that adds an item to the workflow history, the workflow fails.
  17. When you reply to a discussion board item that is created by an anonymous user, you encounter an error if you are an anonymous user.
  18. When SharePoint Designer 2013 workflows contain one or more local variables and there is a disconnected stage, you cannot load the workflows.
  19. When you load a contact list that contains many users in SharePoint Designer 2013, it takes longer than expected.
  20. When you try to create SharePoint Server 2013 workflows in SharePoint Designer 2013, you receive the following error message:

    Retrying last request. Next attempt scheduled in less than one minute.

What are the issues that SharePoint 2013 Service Pack 1 Fixes

Service Pack 1 for SharePoint 2013 and Office product range has been released recently. this is available for all three editions of SharePoint 2013.

Download the Package here – http://technet.microsoft.com/en-us/sharepoint/jj891062.aspx 


  • Make sure that you test the impact of the package in a Test Server (POC) before you apply it to production environments.
  • You don’t need to apply March 2013 CU for this.

And below are the list of issues that Service pack will fix

  1. Metadata is lost when documents that use a custom content type with a "Description" field are opened for editing.
  2. When an item is deleted, restored from recycle bin, and then deleted again, there is a primary key constraint error.
  3. An error occurs when files are moved between document libraries and the web time zone is behind that of the server.
  4. Metadata filtering at list level always lists all metadata terms.
  5. 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.
  6. Multiple-column, SummaryLinkWebParts with a group heading style of "Separator" are rendered incorrectly.
  7. A hash tag that contains a full width space does not get created successfully.
  8. Search schema compression is now enabled by default to allow larger search schemas.
  9. Highlighting for FQL queries is now enabled for FQL as well as KQL.
  10. 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.
  11. 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.
  12. 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.
  13. SharePoint REST API does not return a well-defined error response for a duplicate key exception.
  14. Developers are unable to specify a Content Type ID when creating Content Types in the client object model.
  15. On list views in SharePoint sites, the Connect to Outlook button in the ribbon may be erroneously disabled.
  16. 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.
  17. Copy and Paste in a datasheet does not work correctly with Internet Explorer 11.
  18. Pages do not render in Safari for iPad when private browsing mode is used.
  19. When editing rich text fields in SharePoint, if the editing session exceeds 30 minutes, the edits may not be saved.
  20. 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.
  21. InfoPath may crash when a form that points to a SharePoint list, with a lookup to another SharePoint list, is opened.
  22. An InfoPath form with extended characters in its name fails to open.
  23. 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.
  24. "Show document icon" remains unchecked and the document icon does not show in Edit Properties for a list item.
  25. A "Failed tagging this page" error occurs when the "I like it" button is clicked.
  26. The wrong term is removed when manually editing a multi-valued taxonomy field.
  27. 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.
  28. An error that says "There was an error processing this request" may appear when editing the user profile.
  29. Times are missing from Date/Time results in certain filtered list web service calls.
  30. Minimal and no metadata are now enabled as supported JSON formats. 
  31. Actions4 schema workflow actions can’t be deployed to SharePoint.
  32. Using Client Object Model, Stream.Seek() to seek to a particular position doesn’t seek at the proper offset.
  33. Refreshing a workflow status page generates the following error: "System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary."
    Setting custom, non-English outcomes in web pages on tasks in a workflow fails to set the value.
  34. Configurations of SharePoint using Azure Hybrid mode and Workflow Manager together can cause workflow callbacks to fail.
    Workflow task processes on wiki pages won’t start.
  35. Workflows won’t wait for changes to content approval status fields.
  36. E-mails generated by workflow cannot be disabled for approvals in SharePoint workflows.
  37. Workflows may fail to send an e-mail or send too many e-mails.
  38. Association variables do not update correctly for auto-start workflows.
  39. A KeyNotFoundException error may occur in a workflow when the associated task list uses unique permissions.
  40. Incomplete tasks are deleted when workflow task activities complete.
  41. Task activity is suspended when the task is completed using app-only credentials.
  42. 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.
  43. A workflow doesn’t respond properly when waiting for changes in specific types of list columns, such as Boolean, Date Time, and User.

Failed to create a database. An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Could not find stored procedure ‘sp_dboption’. – Error Occurred when Installing SharePoint 2010 in SQL 2012.

got a new server for my Test environment and started creating a lab of SharePoint 2010 in it with SQL Server 2012 R2. everything went smoothly until I start Configuration Wizard. It came to the 3rd Level and Error Occurred suddenly saying – Failed to create a database. An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Could not find stored procedure ‘sp_dboption’.


After thinking a while realized that my setup was just SharePoint 2010 RTM which is None SP. since my lab is brand new thought of trying on installing SP1. just downloaded and installed the SP1 for SharePoint 2010 and started the wizard again.

Everything Gone perfect after SP1. further when reading understood that it’s must to have SP1/above for SharePoint to install in SQL 2012.

Download SharePoint SP1 here – http://support.microsoft.com/kb/2460045

All SharePoint Updates are here – http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx

August 2013 Cumulative Update Now Available for SharePoint 2013

If your SharePoint 2013 Farm is just RTM, Make sure that you have installed March PU prior to the August Update as it’s mandatory to proceed with future updates.

If you aren’t having March PU, you wont be able to proceed with any later updates and below error will pop out.

“The expected version of the product was not found on the system”


KB 2817517 – SharePoint Foundation 2013

KB 2817616 – SharePoint Server 2013

KB 2817521 – Office Web Apps Server 2013

KB 2817507 – SharePoint Designer 2013

KB 2817615 – SharePoint Server 2013 with Project Server 2013

Note :

Anyway what’s the difference between PU and a CU package. Stefan Gobner has written a informative article for TechNet which I would suggest you to refer on this.

Further information, for Farm which are having Search Components and Highly available search topologies are enabled across servers refer to Kirk Stark’s Article on How to install update packages on a SharePoint farm where search component and high availability search topologies are enabled (which is well described)