Monday, June 18, 2012

SharePoint 2010: April 2012 CU (Update)

So a new CU came out a couple of weeks ago. I've been installing the April 2012 CU in Mid-May on one of my test servers. Since then I noticed some bugs and searched the web for other problems.
Well, the list is not that long, but long enough to mention. It prevented me to update our server used by our customers. Here are some good articles about the original CU version:
- SharePoint April 2012 CU: This hotfix package is no longer available due to a technical problem
- April 2012 CU causing problems with incoming e-mails in SharePoint 2010
- http://msmvps.com/blogs/ivansanders/archive/2012/06/17/update-april-2012-sharepoint-cu-re-release-april-24-2012.aspx

An here is the new version: http://support.microsoft.com/kb/2598151
Including the changes:
UpdateA recent, isolated issue was discovered in the SharePoint 2010 Products April 2012 Cumulative Update that could result in an HTTP 500 error when users delete objects to include documents, lists, and Webs and a new  object is created using the same path where the original object remains in the Recycle Bin. The following packages were affected:

KB2598151 - SharePoint Server Package
KB2598152 - Project Server Package
KB2598321 - SharePoint Foundation Package
KB2598304 – Wss-x-none.msp

Resolution
This issue has been resolved in the revised packages. The revised packages include support for resolving issues related to the originally published updates.

Products Affected
SharePoint Foundation 2010
SharePoint Server 2010
So... Does this fix my problems? Well, stay tuned. I'm installing right now.

*edit 6/19/2012*
I found another really interessting post about the April 2012 CU: April 2012 Cumulative Update – All Changes

But back to my problem: I wasn't able to send emails to a list, in my case a document library. After installing the new CU, I still wasn't able to do so. I had to implement that fix, posted above, again. Which is, in my opinion, a really bad solution.
I'm still hoping for an update that will fix that problem. Do you hear me Microsoft?

No comments:

Post a Comment