October 2017 CU Site Creation Error for SharePoint Foundation 2013

EDIT 11/14/2017: This is resolved in the November 2017 CU, specifically KB4011256.

When attempting to create a Site Collection via Central Admin in SharePoint Foundation 2013 using the October 2017 Cumulative Update, you will encounter an error when attempting to load the page (/_admin/createsite.aspx).

ULS will show the following.

In addition, the Configure hybrid OneDrive and Sites features page (/_admin/cloudconfiguration.aspx) under Office 365 in Central Admin will also generate an error.

And the ULS message associated with Hybrid configuration:

So why are we getting this error? Well, when we run the Microsoft.Office.Server.UserProfiles.dll through PEVerify, we end up with a plethora of errors like this:

Essentially, this means there are no return values possible from the method. And indeed, when we reflect the binary we can see why in the method Microsoft.Office.Server.UserProfiles.ProfileLoader.GetUserProfile(). Here is the September 2017 CU binary:

Compare that to the broken October 2017 CU binary:

With the October 2017 CU binary, it appears most of the UserProfile (and other methods) have been blanked out in a similar fashion.

For Site Creation, it appears that it is still possible to create new sites via New-SPSite. It does not appear that it is possible to manage the Office 365 Hybrid OneDrive for Business and Sites configuration. This particular issue will have to wait for a fix from Microsoft.

A big thank you to Todd Klindt for raising this issue!

 

33 Comments

  1. The issue as well occurs while trying to create subsites on existing Site Collections using the newsbweb.aspx site.

    • I’ve been able to successfully create subwebs on pre-Oct 2017 CU sites as well as sites created using New-SPSite post-Oct 2017 CU using newsbweb.aspx.

      • Interesting. I have a customer dealing with this issue attempting to create subwebs/accessing the newsbweb.aspx website.
        Unexpected Errors are logged in ULS Logs :

        System.InvalidProgramException: Common Language Runtime detected an invalid program.

  2. Foundation farms with October PU are also affected.
    Installation was September CU + October PU

    • This is correct. I haven’t installed the October CU only the October Security Update and we’re unable to create subsites. Off to use powershell….

      System.InvalidProgramException: Common Language Runtime detected an invalid program.
      at Microsoft.SharePoint.WebControls.TemplatePicker.RegisterWebTemplateClientScript()
      at Microsoft.SharePoint.WebControls.TemplatePicker.OnPreRender(EventArgs e)
      at System.Web.UI.Control.PreRenderRecursiveInternal()
      at System.Web.UI.Control.PreRenderRecursiveInternal()
      at System.Web.UI.Control.PreRenderRecursiveInternal()
      at System.Web.UI.Control.PreRenderRecursiveInternal()
      at System.Web.UI.Control.PreRenderRecursiveInternal()
      at System.Web.UI.Control.PreRenderRecursiveInternal()
      at System.Web.UI.Control.PreRenderRecursiveInternal()
      at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

  3. So this really only applies to SharePoint Foundation 2013 – not applicable to SharePoint Server 2013?

  4. Has anyone seen this occur on Enterprise 2013? Wondering if there might be a build difference there and this bug is only associated with Foundation 2013 builds.

  5. I am also getting this bug for SP 2013 foundation. I can not find anywhere to submit it to MS. This needs to be fixed ASAP! Thank science for patch testing!

  6. I’m getting an error clicking on MySites setup on SP2013 Enterprise, it’s related to the Microsoft.SharePoint.WebControls.HybridOneDriveDefaultToCloudCommon.GetHybridMySiteUrl()
    Am I the only one?

    • Same here Mia. Currently multiple SP2013 Server (not Foundation!) affected at one of my customers who installed September CU and October PU.

      Easy to reproduce: Inside the User Profile Service Application you just have to click on “Setup My Sites” and you’ll receive following Error:
      Could not load type ‘Microsoft.SharePoint.WebControls.HybridOneDriveDefaultToCloudCommon’ from assembly ‘Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’.

    • Hi Mia,
      October 2017 CU fixes the ‘Setup Mysites’ issue (this should be also valid for November 2017 CU).

  7. We installed security updates as part of monthly updates on production server. Users cannot create new sites.
    Is there a fix for it ?
    Please advise.

  8. Good news for all affected farms:

    The fix for this issue is released in Nov 2017 CU. Trevor wrote about the availability of the CU yesterday (https://thesharepointfarm.com/2017/11/sharepoint-2013-november-2017-updates/)

    KB 411258 (https://support.microsoft.com/en-us/help/4011258/november-14-2017-update-for-sharepoint-foundation-2013-kb4011258) which is part of this fix explains this fix. Here is the excerpt from the KB.

    “After you install the October 10, 2017, cumulative update for SharePoint Enterprise Server 2013 (KB4011177), you cannot create sites in SharePoint Server 2013 if there’s no User Profile service application configured.” (As we figured out, the issue also occurs just by installing the Oct PU).

  9. Guys,
    Can someone post a solution for this issue?

    • Hi Chandra!
      As stated by Trevor on the very top of the page (update from Nov 14th) – as well as my last comment from Nov 15th – you’ll see that the November 2017 CU is fixing this issue.

      This fix was also confirmed by my colleagues from Premier Support.

  10. Hi Christian,

    It states that the fix is for “Foundation” but in the description, it talks about Server.
    I installed the update (KB4011256), but no change. That is, the error message is now “An unexpected error has occurred.” But still no new sites.
    In ULS, it remains the same “Common language…” message.
    Is Premier Support confirming for Foundation or Server or both?

    Thanks,
    Peter

  11. Hi Trevor , after going through your blog http://www.toddklindt.com/blog/Regressions/sp2013Nov2017cu.aspx in the Regression doesn’t seem any issue identified , Do you know if this implies October patch issue (site creation) is resolved/fixed by this CU ?

  12. Anyone know if the November 2017 CU fixes this regression (site creation break) found in the October 2017 CU? I’m looking at installing KB4011251 tomorrow.

  13. Important news for everyone who is still facing this issue, even after installing the November CU, that is supposed to provide a fix (https://support.microsoft.com/en-us/help/4011256/november-14-2017-update-for-sharepoint-foundation-2013-kb4011256):

    This issue is – again – explicitly addressed with the latest CU from December 2017 (https://support.microsoft.com/en-us/help/4011596/december-12-2017-update-for-sharepoint-foundation-2013-kb4011596)

    The misbehavior was not resolved for all affected environments, therefor the current CU from December is supposed to finally fix it

  14. I am still having this issue after installing the December CU. Is anyone else still having this issue?

    Any known work arounds as we still cannot create sub sites?

    • What error(s) are you seeing? Does the ULS log indicate anything?

      • I seen that the January CU is available, going to try installing that in the morning, fingers crossed.

        Here’s the log:
        Application error when access /_layouts/15/newsbweb.aspx, Error=Common Language Runtime detected an invalid program.
        at Microsoft.SharePoint.WebControls.HybridOneDriveDefaultToCloudCommon.get_IsOneDriveDefaultToCloudEnabled()
        at Microsoft.SharePoint.WebControls.TemplatePicker.RegisterWebTemplateClientScript()
        at Microsoft.SharePoint.WebControls.TemplatePicker.OnPreRender(EventArgs e)
        at System.Web.UI.Control.PreRenderRecursiveInternal()
        at System.Web.UI.Control.PreRenderRecursiveInternal()
        at System.Web.UI.Control.PreRenderRecursiveInternal()
        at System.Web.UI.Control.PreRenderRecursiveInternal()
        at System.Web.UI.Control.PreRenderRecursiveInternal()
        at System.Web.UI.Control.PreRenderRecursiveInternal()
        at System.Web.UI.Control.PreRenderRecursiveInternal()
        at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

  15. Applied the January CU and it DID fix this issue

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.