ISSUE: KB2844286 RESOLVED with Update KB2872441

Microsoft has finally released an update to the KB2844286 issue with SharePoint. That update is linked below.

We have installed it in our DEV environment and have verified the issue is fixed within our farm. I have also confirmed that you must still have KB2844286 installed and then install KB2872441 as you will still need the other security related patches from KB2844286 (or KB2844285, or KB2844287 depending on OS)

My original post can be found below as I am still updating that post as I get updates.

ISSUE: KB2844286 Security Update on SharePoint 2010


ISSUE: KB2844286 Security Update on SharePoint 2010

Came in today to find the following error message showing up on seemingly random web parts and lists throughout our SharePoint 2010 Foundation farm. ULS Logs on the servers weren’t very helpful.

[This issue has been RESOLVED see updates below]

KB2844286 Error

For the sake of search indexing, here is the text version of the error we are getting.

Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator.

We quickly tracked it down to a Security Update that was applied to our web front end servers last night. Check the OS below to find the KB update associated with your server.

Windows XP and Windows Server 2003

Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1

Windows Vista Service Pack 2 and Windows Server 2008 Service Pack 2

This is in regard to the following Microsoft Security Bulletin for July 2013

Microsoft Security Bulletin MS13-052

As a temporary workaround, we found uninstalling the update (KB2844286) from your servers (all WFE’s and App servers) then performing an IISReset on the servers will resolve the issue. Several others have experienced this issue as noted in just one of many forums such as the one below

If I find there is a solution better than uninstalling I will update this post to reflect that. As of right now, uninstalling this update is the best option.

[Update 7/16/2013 3:40pm]

It appears the error typically appears when a list or web part view has had the XSLT customized. At least in our Farm, that has been the common behavior.

[Update 7/17/2013 10:03am]

Not much of an update, but I’m awaiting contact from our Microsoft TAM to see about this issue. If we don’t hear from them soon, then we’ll be opening a ticket with Microsoft. Luckily we were able to work around the issue by uninstalling.

[Update 7/17/2013 12:50pm]

I just received confirmation from our TAM that Microsoft is aware of 2 issues regarding the patch noted in this article above. One of which appears to be the SharePoint issue we’re having.

[Update 7/17/2013 2:43pm]

Just spoke with our Microsoft Sr. Support Escalation Engineer assigned to our premier support ticket and here is their response (summarized).

“Our product group is currently working on the updated patch. We have no ETA for the new release at the moment.”

Looks like we wait then for a resolution.

[Update 7/17/2013 2:59pm]

One more confirmation from Microsoft Support and a link to the forum MS is using to track the issue publicly. No public information just yet beyond that, however.

“Both the SharePoint and .NET product groups are aware of the issue and they are in the process of fixing the patch.”

Follow the issue at this TechNet Forum

[Update 7/18/2013 9:24am]

So far I have heard of no updated patch being released yet by Microsoft. There were two MS Security Bulletin updates but it doesn’t appear they were related to this issue as they were for Bulletin MS12-006 and MS12-052.

[Update 7/21/2013 12:36pm]

Still no updated patch. Received an e-mail from our MS Support representative and they indicated they too have no ETA on any updates to the security patch. I guess I’d rather they take their time then rush an update out all to break something else. It would be a good idea if Microsoft were to either add a note to the update download page indicating the issue, or just pull the update altogether.

[Update 7/24/2013 8:28am]

I just got a message from our Microsoft Support representative and she informed me there is no update as of yet on a new download for the patch. No surprise there.

[Update 7/25/2013 7:50am]

As you can see from the comments that have arrived thus far, it appears Microsoft has provided a fix to the KB2844286 issue. We are in the process of testing it out in our DEV environment now. Let’s hope it fixes it and doesn’t cause more issues.

[Update 7/25/2013 8:22am]

I am at this point, comfortable with counting this issue RESOLVED. We’ve tested it in DEV and the solution resolves the problem and doesn’t seem to break anything else. We won’t be able to complete the resolution in our Production environment until after hours as we will have to re-install KB2844286 which will require a reboot and the patch requires at the very least an IISRESET.

Go to to download the update. Note: You will need to run an IISRESET for the update to take effect after installing.

Mail Merge Using SharePoint List as Data Source

I have found several articles on the web that made mail merge using a SharePoint 2010 list as the data source possible which has spawned this post. The instructions I found online were great, up to a certain point, however. Most of the instructions assumed the users had some basic understanding and thus many steps were omitted which reduces the target audience that can use their instructions considerably. These instructions are intended for folks who have not worked with the Visual Basic Macro editor and don’t have a lot of interest in learning how to do it. They just want to get their work done.

Setup Info

I have created the following test documents and test SharePoint lists for these instructions. You will need to do the same for your project.

Files/Data Used

  • Create Data Source list in SharePoint 2010
  • Open Notepad and save an empty file as TestMergeSource.odc to the following location
    • C:\Program Files (x86)\Microsoft Office\Office14\QUERIES
  • Open Microsoft Word (2007 or 2010)
  • Save Word document as TestMergeDocument.docx to SharePoint 2010 document library location noted above
  • In Word document click View tab
  • Click View Macros (see below)
  • Enter a name in the Macro name: field (no spaces)
    • I named mine Test_Merge_Source
  • Select All active templates and documents in the Macros in: drop down (see below)
  • Click Create button
  • Paste the below code into the Visual Basic Editor replacing bolded sections with your filenames
    • (NOTE: If you have more than one macro, your editor may have multiple Sub sections, this is ok)
Sub Test_Merge_Source()
Test_Merge_Source Macro
‘ Combines files to produce form letters, mailing labels, envelopes, and catalogs
‘ List name
Const strList As String = “Mail Merge Data Source
‘ Site URL
Const strDatabase As String = “
‘ Office Database Connection file
Const strODC As String = “C:\Program Files (x86)\Microsoft Office\Office14\QUERIES\TestMergeSource.odc
ActiveDocument.MailMerge.MainDocumentType = wdNotAMergeDocument
ActiveDocument.MailMerge.OpenDataSource _
Name:=strODC, _
Connection:= _
“Provider=Microsoft.ACE.OLEDB.12.0;” & _
“Data Source=” & strDatabase & “;” & _
“Mode=Share Deny None;” & _
“Extended Properties=””WSS;HDR=NO;IMEX=2;” & _
“DATABASE=” & strDatabase & “;” & _
“LIST=” & strList & “;””;”, _
sqlstatement:= _
“SELECT * FROM [” & strList & “]”
End Sub
  • Your completed code will look like the image below with no other Macros present, if you do have others your code will look different
  • Click Save when done
  • Close the Visual Basic Editor screen
  • Back in Word click the Macros button and click View Macros again
  • You should now see the newly created Macro named Test_Merge_Source (or whatever you named yours… see below)
  • Select your Macro and click Run
  • Click the Mailings tab
  • Click the Edit Recipients List button in the Start Mail Merge section
  • Validate the recipients list is accurate (see below)
  • If all is correct, create your document as you normally would and then save the document.
  • You will not need to repeat these steps unless you move to a different computer or remove the code added above

You can also use this macro for other Word Documents that you want to use the same data source. This is why I recommend saving the macro with a name specific to the data source (SharePoint List).

 If these instructions were helpful please leave a comment or if you had issues understanding/following them please leave feedback so I can fix them.