SharePoint 2013 and April CU 2014 issues.

Due to the problem identified in SP1, the  global installation package has not been released yet an. If your business has some urgency to have this issue fixed you can install the single package without any impact in your supportability.

Our full-server packages (SharePoint Server and Foundation) are not yet available and therefore you could install only “sub-packages”. From support perspective we are always suggesting to install full-server packages, but in case you need an important April 2014 CU hotfix, just for your info.

SharePoint contains not only SharePoint components and therefore the following list may not exhaustive.

General information you can find here: http://support.microsoft.com/kb/2953733

Access Server Download Link
Contains fixes when SQL Server 2014 will be used.

OWAS 2013 has an own kb article:
2863899    Description of the Office Web Apps Server 2013 hotfix package (Wacserver-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863899
For this package you need to have a SlipStream installation of OWAS2013 including SP1 or you can install it on top of any other former CU.

SharePoint Server 2013 Oserver package
2760265    Description of the SharePoint Server 2013 hotfix package (Oserver-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2760265

SharePoint 2013 / Word Server
2768332    Description of the SharePoint Server 2013 hotfix package (Wdsrv-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2768332

SharePoint Server 2013 Coreserver package
2863887    Description of the SharePoint Server 2013 hotfix package (Coreserver-x-none.msp; Projectserverwfe-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863887

SharePoint Server 2013 Client Components package
2863895    Description of the SharePoint Server 2013 Client Components SDK hotfix package (Spdevsdk-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863895

More Info
http://blogs.msdn.com/b/joerg_sinemus/archive/2014/04/09/sharepoint-2013-and-09-april-2014-status.aspx

 

 

February 2014 CU for SharePoint 2010 has been released

The product group released the February 2014 Cumulative Update for the SharePoint 2010 product family.

Be aware that the February Cumulative Update for SharePoint 2010 is a Post-SP2 hotfix. It is recommended to have SP2 installed before installing the February CU

More details please check;
http://blogs.technet.com/b/stefan_gossner/archive/2014/02/12/february-2014-cu-for-sharepoint-2010-has-been-released.aspx
http://blogs.msdn.com/b/joerg_sinemus/archive/2014/02/12/sharepoint-2010-and-february-2014-cu.aspx

 

Keynotes for Distributed Cache on SharePoint 2013

My colleague Hector has created a very good article by compiling different issues with Distributed Cache.
You can read the orginal article below link:
http://blogs.msdn.com/b/calvarro/archive/2013/08/29/points-to-consider-with-distributed-cache-on-sharepoint-2013.aspx

Here is the key notes:

  • NEVER admin the distributed cache from the admin console
  • Maximum capacity of memory is 16 GB per host cache
  • Dynamic memory is not supported in SharePoint 2013 environments nor APP fabric servers
  • The prodcuct after being installed allocates 10% of the physical RAM memory available at the sever. It can be configured following the next point.
  • It’s recommended to allocate 2 GB for other services.
  • It’s not supported to develop code against the Distributed Cache of SharePoint 2013.
    “If you are using custom applications in SharePoint Server 2013 which use the AppFabric client APIs, or are creating custom caches, you should create a separate AppFabric cache cluster to support your custom applications. Do not use the AppFabric cache cluster supporting your SharePoint Server 2013 farm. Run your separate AppFabric cache cluster for your custom applications on separate servers from the servers dedicated to your SharePoint Server 2013 farm.
    http://blogs.msdn.com/b/calvarro/archive/2013/06/05/supportability-of-custom-developments-in-sps-2013-and-appfabric-cache.aspx
  • Install the latest APP Fabric CU if possible. Right now we are in CU 4

SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging

The following change was made to the December 2013 Cumulative Update from the previous SharePoint Server 2013 rollup updates. Previously, SharePoint 2013 Cumulative Updates included both the executable and the .CAB file in the same self-extracting executable download. Due to the file size, the SharePoint Server 2013 package has been divided into two separate downloads in December 2013. One package contains the executable file (identified as ubersrv2013kb2850024fullfilex64glb), while the other contains the .CAB file (identified as ubersrv_1). Both are necessary and must be extracted to the same folder to successfully install the update. Both are available via the same Hotfix Download Available link in the KB article for the December 2013 SharePoint Server Cumulative Update release.

For more information:
http://blogs.technet.com/b/office_sustained_engineering/archive/2013/12/20/change-sharepoint-2013-rollup-update-for-the-december-2013-cumulative-update-packaging.aspx

 

December 2013 CU for SharePoint 2013 has been released

Be aware that all Update for SharePoint 2013 require March 2013 PU for SharePoint 2013 to be installed first.

Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled.

ATTENTION:

Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into two separate downloads. One contains the executable file (identified as ubersrv2013kb2850024fullfilex64glb), while the other contains the .CAB file (identified as ubersrv_1). Both are necessary and must be extracted to the same folder to successfully install the update. Both are available by clicking the same Hotfix Download Available link in the KB article for the release.

See the KB article of the SharePoint Server CU for more details.

KNOWN ISSUE:

After installing the SharePoint 2013 Server December 2013 CU PerformancePoint Dashboard Designer no longer loads. When you try to open Dashboard Designer in SharePoint 2013, you receive an error message. You should not install the SharePoint Server 2013 CU listed below if you need PerformancePoint Dashboard Designer.

See the KB article of the SharePoint Server CU for more details.

For More Info:

http://blogs.technet.com/b/stefan_gossner/archive/2013/12/20/december-2013-cu-for-sharepoint-2013-has-been-released.aspx

 

August CU 2013 has been released.

August 2013 CU for SharePoint 2013 has been released
http://blogs.technet.com/b/stefan_gossner/archive/2013/08/14/august-2013-cu-for-sharepoint-2013-has-been-released.aspx

August 2013 CU for SharePoint 2010 has been released
http://blogs.technet.com/b/stefan_gossner/archive/2013/08/14/august-2013-cu-for-sharepoint-2010-has-been-released.aspx

Note For SP2:
* It is recommended to install June 2013 CU before SP2. June 2013 CU might not correctly identify the SP2 baseline. If SP2 has already been installed and June CU does not install you need to install  August CU which will correctly identify the SP2 baseline.

June 2013 CU for SharePoint 2010 has been re-released

“The product group has now re-released the June 2013 Cumulative Update for the affected products including SharePoint.Be aware that the KB article numbers of the re-released Fixes are different from the original ones.The KB articles are not yet available but should be in the next couple of days. The fixes can already be downloaded. It is strongly recommended that customers who installed the initial June CU install the re-released updates.”

http://blogs.technet.com/b/stefan_gossner/archive/2013/07/11/june-2013-cu-for-sharepoint-2010-has-been-re-released.aspx

http://blogs.msdn.com/b/joerg_sinemus/archive/2013/07/11/update-sharepoint-2010-and-june-2013-cu.aspx