| (See the solution for this issue at the end of this blog post)
Don’t you hate it when a hero lets you down? Like when Nicolas Cage decided to star in Ghost Rider. Twice! That’s how it goes sometimes. Unfortunately that’s how it went with the December 2012 Hotfix for SharePoint 2013. After you install this patch on SharePoint Server 2013 users can no longer create MySites. Existing MySites still work, but no more can be created. When users try to create a MySite you’ll find an error like this in your ULS logs:
01/03/2013 00:32:34.59 OWSTIMER.EXE (0x05F0) 0x0C1C SharePoint Portal Server Administration 5187 Critical My Site creation failure for user 'CONTOSO\user1'for site url 'http://my.contoso.com/personal/user1'. The exception was: System.MissingMethodException: Method not found: 'Microsoft.SharePoint.SPSite Microsoft.SharePoint.SPSite.SelfServiceCreateSite(System.String, System.String, System.String, UInt32, Int32, Int32, System.String, System.String, System.String, System.String, System.String, System.String, System.String, System.String, Microsoft.SharePoint.SPSiteSubscription)'. at Microsoft.Office.Server.UserProfiles.UserProfile.<>c__DisplayClass2.<CreateSite>b__0() at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode) at Microsoft.Office.Server.UserProfiles.UserProfile.CreateSite(String strRequestUrl, Boolean bCollision, Int32 overrideCompatLevel, Int32 lcid). 2611f19b-b123-1001-13a4-5ae2bd6a86be
The key to the problem is highlighted, the User Profile Service is trying to create the MySite with a method that doesn’t exist. It looks like regular Self Service Site Creation still works. Full notes on this patch can be found on my SharePoint 2013 Builds wiki.
There’s no way to uninstall SharePoint patches, so if you’ve installed this patch you’re stuck with it. Hopefully this will be fixed in the next CU or Hotfix.
You can keep up with all the SharePoint 2013 Patches by visiting my SharePoint 2013 Builds page and following SharePoint2013Patches on Twitter.
I’d like to thank Ali Salih and Jason Himmelstein Blog | Twitter) for bringing this to my attention and Trevor Seward (Blog | Twitter) for helping me reproduce and troubleshoot it.
Edited to add:
This problem can be fixed with the installation of another December 2012 Hotfix, KB2752001.
tk
ShortURL: http://www.toddklindt.com/SP2013December2012HotfixRegression
Edited 1/25/2013 |