Hot answers tagged

4

SharePoint 2010 only works properly in IE9, IE10, and IE11 when the compatibility meta tag is set to IE8. It does not support IE9/10/11 in their native rendering modes. There is no actual work around for this, it is a known issue with SharePoint 2010. The SharePoint 2010 controls only work in IE8 mode.


4

First, you should be aware of the SharePoint Security Fixes that included within the Windows Update will not be reflected until running the SharePoint Configuration Wizard Second, It's recommended to don't include the SharePoint Security Fixes with the windows update to avoid your current confusion. However, if you will install the SharePoint Security ...


2

I communicated with Stefan Gobber who is escalation engineer at Microsoft about SharePoint security fixes through MU/WU he said SharePoint fixes for server products will continue to be available via Microsoft Update. Install CU if it will fix issue on farm, Never install CU on production till apply it on test. I tried to summarize our conversation and ...


2

Trevor already give you details on this. I tell what we do. We prefer CU on security patches but if there is service pack then that is our priority. We never install every cu unless it fix one of the issue related to our farm. As CUs are cumulative and contains previous cu fixes, So we apply CU in our farm every 3rd quarter. Reason, this required down time,...


2

SharePoint updates should not be installed via MU/WU as they require manual intervention post-installation through the Config Wizard. As for CU vs. Security, totally up to you and your testing. CUs include all updates between the previous Service Pack (and/or RTM) and the current month, including the security update. CUs generally require more testing on ...


2

I ran into this issue today - specifically ActiveX not being recognized as available so Datasheet view didn't work on a list. (Edit 2014-07-10: This works to fix SharePoint 2013 pre-SP1 as well e. g. not being able to work with web parts in edit mode.) There are two fixes to this on the client side, but they are both very big hammers: You can add the site ...


2

This errors also happens if you have done installation on wrong order. I have seen this issue if you have installed first sharepoint CU and then Foundation CU. it should be always first Foundation and then SP Servers update.


2

The problem was a issua of a Microsoft Update in my server. I found some forums relating the same problem. Was installed in my Windows Server 2008 R2 Service Pack 1 the KB2844286 Security Update. To fix it you can unistall KB2844286 or you can install an update in http://support.microsoft.com/kb/2872441 More details see http://techchucker.wordpress.com/...


1

I had a similar issue when trying to bring an additional WFE server online. The problem relates to the installation media. SharePoint including SP1 is missing something or has an issue which causes you to always be missing this hotfix. Instead use the non SP1 media and then install all the updates and it will work just dandy.


1

I am not sure how are installing the hotfixes or service packs but you should install any WSS 3.0 cumulative update before installing the corresponding MOSS 2007 cumulative update. The recommended sequence for installing the updates is as follows: Latest WSS 3.0 Service Pack released prior to the Cumulative Update Latest MOSS 2007 Service Pack released ...


Only top voted, non community-wiki answers of a minimum length are eligible