Hi Stefan
Any advice on what to install to stay “supported”
Based on this I would need to install the April 2017 PU at a minimum
What would MS be looking for when a user calls premier support?
Would not having the April 2017 PU keep new patches from being installed
“https://technet.microsoft.com/library/684173bb-e90a-4eb7-b268-b8d7458bc802(v=office.16).aspx”
we have patched till SP1 in our farm, is it OK to directly install AUG 2017 CU directly ?
Yes, thats the way to go.
August 2017 CU includes everything since SP1.
Hi Dominick,
after April 2017 only security fixes will created – no regular CUs as regular CUs are only created during mainstream support.
Newer security fixes should also install on older CUs but if you are in a need to get support from Microsoft and you are on an older CU you will have to apply one of the supported CUs first.
Cheers,
Stefan
Thanks for the quick reply 🙂
I tried that, but it still gives the same error :\
Hi Matt,
I tested your code and it works for me – of course it fails internally because b64 is an empty string and no valid assembly can be created from it.
But I do not get a TargetParameterCountException.
Cheers,
Stefan
We are encountering the same issue after applying the security updates. The createsite.aspx page throws “Sorry Something Went Wrong” and “Common Language Runtime detected an invalid program” error. This is on a SharePoint 2013 Foundation farm that previously worked fine.
Hi Ken,
in this case I would recommend to open a support case with Microsoft to get this analyzed.
Cheers,
Stefan
Hi Stefan,
After installing this CU we are unable to create any sites. This issue is also mentioned at http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=346 that multiple people have had this issue.
The error is
Application error when access /_layouts/15/newsbweb.aspx, Error=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) e041269e-de3e-802d-746e-7d3742eb2725
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) e041269e-de3e-802d-746e-7d3742eb2725
Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> 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)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) e041269e-de3e-802d-746e-7d3742eb2725
Cheers
Jatin
Hi Jatin,
please ensure to open a support ticket for this to request a fix.
Cheers,
Stefan
Hi – extended support ends 4/11/2023. We are not ready for migration to 2016 and looking at hybrid anyway 🙂
Correct – but extended support is limited. E.g. no hotfixes can be requested for SharePoint 2013 after end of mainstream support.
Sounds like this is an issue with just Foundation: https://thesharepointfarm.com/2017/10/october-2017-cu-site-creation-error-sharepoint-foundation-2013/
Standard, Enterprise, and Project builds aren’t experiencing the problems.
Hi Stefan,
When checking September monthly security update for SharePoint 2013 we have three updates :
https://support.microsoft.com/en-us/help/3213560/descriptionofthesecurityupdateforsharepointserver2013september12-2017
https://support.microsoft.com/en-us/help/4011113/descriptionofthesecurityupdateforsharepointserver2013september12-2017
And
https://support.microsoft.com/en-us/help/4011117/descriptionofthesecurityupdateforsharepointfoundation2013september12-2
Are we supposed to install all three ? my concern is if we install server updates we don’t necessarily need to update Foundation since that already included in server ?
Hi Mohanghimire,
the SharePoint server security fixes do not include the SharePoint foundation fixes. You need to install all of them.
For the CUs we have server or “uber” packages – which I reference in this article. The “Uber” packages for SharePoint Server include the SharePoint Foundation fixes.
Cheers,
Stefan
Hi Stefan,
I couldn’t help but notice that with this CU the size of ubersrv_2.cab suddenly dropped to 277.9 MB, after staying in a range of 335 to 340 MB for the previous year of updates. That was a real red flag for me! Where these are cumulative, I always assumed the CAB files would stay around the same size or grow in size from month to month.
Hi John,
everything is fine here!
The packaging team identified some packages being included in our previous CUs which contained fixes which were released between RTM and SP1. As our patches can only be installed on SP1 the packaging team decided to remove the additional unnecessary packages.
Cheers,
Stefan
Thanks for that. Is it possible the error is caused by my choice of exes to convert to b64 and use?
I created a winforms project and built it without adding anything, converted that to b64 and it runs perfectly. Other exes I’ve tried have been various things I’ve downloaded – installers etc. I guess their dependencies and such cause issues when running the program in this manner.