Steve Chen [MSFT] Sr. Support Escalation Engineer

...about SharePoint mysteries and related

Blogs

June 2011 CU for SharePoint 2010 and MOSS 2007 released

  • Comments 5
  • Likes

The June 2011 Cumulative Update for the SharePoint 2007 and SharePoint 2010 Server product family have been published now.

MOSS/WSS:

2544399 The full server package for WSS
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2544399

2544398 The full server package for MOSS
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2544398

Download and installation information:

As usual:
After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or
“psconfig –cmd upgrade –inplace b2b -wait”
in command line. This needs to be done on every server in the farm with SharePoint installed.

For all previous updates and packages, please see also my “Build Numbers and Cube Sheet MOSS/WSS” 


SharePoint 2010/Foundation:

Ee721049.note(en-us,office.14).gifNote:
It is highly recommended to install first the Service pack 1 for SharePoint 2010 and afterwards the June CU!
Please see also related information here: http://blogs.technet.com/b/steve_chen/archive/2011/06/07/3433939.aspx

MSF2010:
2536601 The full server package for Microsoft SharePoint Foundation 2010
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2536601

Download link: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2536601&kbln=en-us

SPS2010:
2536599 The full server package for SharePoint Server 2010 and contains also the MSF2010 fixes so you need only this one package.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2536599

Download link: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2536599&kbln=en-us

Further instructions and information:

After installing the packages, you may be prompted for a reboot of your Server! Please don’t forget to run the PSConfig Wizard anyway, even after reboot just to ensure that all updates has been applied completely and successful! As usual, you can use the command line on each server in Farm:   “psconfig –cmd upgrade –inplace b2b -wait”

News in June CU reagrding User profile Sync Service! 
Spencer Harbar has also recently posted the news about the changes that the June CU offers now for the User rpofile sync service.
Please see his full post here: http://www.harbar.net/archive/2011/07/08/upsjun11.aspx

June 2011 CU re-released due to some known problems, described in the according KB articles to the hotfixes!
See more here: http://blogs.technet.com/b/stefan_gossner/archive/2011/07/12/june-2011-cu-for-sharepoint-2010-has-been-re-released.aspx

If not downloaded the latest version for June CU, please get the fresh bits again and install them on top to ensure that you have the fixed packages!

Please vsiit also the Post from Jie Li, "The Mystery Behind SharePoint 2010 Patching" it will calrify some further questions about the patching mechanism.

Major changes to FIM applied within the June 2011 CU:

With the June 2011 CU packages we also have updated the FIM bits. The new build of FIM in the June 2011 CU is now 4.0.2450.34.
Please see more Info and all prior Build versions for FIM on Spencer's Post here: User Profile Synchronization Service changes in the June 2011 Cumulative Updates

 

Known issues:

A colleague posted about a side effect which shows its behavior as described below:

Symptom:
User Profil import stops working with  stopped-extension-dll-exception” errors in miiserver.exe (FIM Agent)

Error Details:

"System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.PlatformNotSupportedException: Microsoft SharePoint is not supported with version 4.0.30319.235 of the Microsoft .Net Runtime.
   at Microsoft.SharePoint.Administration.SPConfigurationDatabase.get_Farm()
   at Microsoft.SharePoint.Administration.SPFarm.FindLocal(SPFarm& farm, Boolean& isJoined)
   at Microsoft.SharePoint.WebControls.SPControl.SPWebEnsureSPControl(HttpContext context)
   at Microsoft.SharePoint.SPContext.get_Current()
   at Microsoft.Office.Server.UserProfiles.ProfileManagerInstance.GetApplicationProxy()
   at Microsoft.Office.Server.UserProfiles.ProfileImportExportService.FinalizeProfileImportExportProcess(Int64 importExportId)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.Office.Server.WebServiceDirectProxy.WebMethodInfo.Invoke(Object webServiceInstance, Object[] args)
   at Microsoft.Office.Server.WebServiceDirectProxy.Invoke(String methodName, Object[] args)
   at Microsoft.Office.Server.UserProfiles.ManagementAgent.ProfileImportExportDirect.FinalizeProfileImportExportProcess(Int64 importExportId)
   at Microsoft.Office.Server.UserProfiles.ManagementAgent.ProfileImportExportExtension.Microsoft.MetadirectoryServices.IMAExtensibleCallExport.EndExport()
Forefront Identity Manager 4.0.2450.34"

See the highlighted part:  it runs on .net 3.5 and not on .net 4.0 !

As a solution we have two options:

1. Workaround:  uninstall .net 4.0 from Windows Server

2. Workaround: configure process execution  (better approach)

Wrkaround to force FIM to use the .NET Framework v2.0 version:
1. Open the c:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\Bin\miiserver.exe.config file for editing.
2. Locate the below section:

<startup useLegacyV2RuntimeActivationPolicy="true">
   <supportedRuntime version="v4.0.30319"></supportedRuntime>
   <supportedRuntime version="v2.0.50727"></supportedRuntime>
 </startup>

3. Delete or comment out the reference for the .NET v4 version. Like this:

<startup useLegacyV2RuntimeActivationPolicy="true">
  <!-- <supportedRuntime version="v4.0.30319"></supportedRuntime> –>
  <supportedRuntime version="v2.0.50727"></supportedRuntime>
 </startup> 

or

<startup useLegacyV2RuntimeActivationPolicy="true">
     <supportedRuntime version="v2.0.50727"></supportedRuntime> 
 </startup>

4. Restart the two FIM services in the services console.
5. Run the sync again.

----------------------------------------------------------------------------------

Other related Links:

A complete list of all published SharePoint CU’s and updates per version is found here: 

SharePoint Server and Foundation 2010 Build numbers and updates

Office SharePoint Server 2007 (MOSS) and Windows SharePoint Services 3.0 (WSSv3)

SharePoint Portal Server 2003 and WSSv2

All about updating MOSS and Language Packs

The Mystery Behind SharePoint 2010 Patching by Jie Li

 

Related Update and resource Centers:

 


Project Server 2010:

Software updates include any update, update rollup, service pack, feature pack, critical update, security update, or hotfix. See KB 824684 for a description of the standard terminology that is used to describe Microsoft software updates. See KB 953878 for information about cumulative updates that are available from the Microsoft Office team to fix reported problems.

For detailed information about applying Project Server 2010 cumulative updates, see Deploy cumulative updates.

For the latest public updates, see the Update Center for Microsoft Office, Office Servers, and Related Products.

Service Pack 1 (SP1)

For more information, see TechNet Webcast: Information about Project 2010 and Project Server 2010 Service Pack 1 (Level 200).


Comments
  • Hi Steve,

    Any word on whether the MyMemberships issue was fixed in either SP1 or the June 2011 CU? My users are anxiously waiting! Thanks.

  • Hi Eric,

    regarding the Membership issue, the awaited fix is postponed to august 2011 cause they need more time to fix it correctly and thus it did not make it up into the June CU as expected.

    So it seems that we still must wait until the FIX hopefully will be published, sorry for the bad news but that's it by now.

    regarding your caveat with the recreated UPA, did you also created new social-, Sync and profile databases?

    The social tags are stopred mostly in the Social DB, maybe when you reattach the old DB, this would bring the tags and data back without erissuing the mebership issue...  I didnt test this due to lack of time but would be worth a try, surely first in a test environment ;-)

    cheers, Steve

  • Hi Eric,

    check out the August 2011 CU regarding Membership issue - should be fixed with that update ;-)

  • thank you

    really i like it

  • thanks

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment