Sharepoint 2016 on premise - autoeventwireup error after September 2020 patch

Vincent Jourdain 11 Reputation points
2020-09-14T15:05:41.293+00:00

Hi,

We have ghostable pages that are using autoeventwireup.

Since we deployed the September patch, we are getting "autoeventwireup is not allowed for this page".

Please Help

Microsoft 365 and Office | SharePoint Server | Development
0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. Vincent Jourdain 11 Reputation points
    2020-09-14T15:56:47.033+00:00

    Getting Error Message for Exception System.Web.HttpParseException (0x80004005): The attribute 'autoeventwireup' is not allowed in this page. ---> System.Web.HttpParseException (0x80004005): The attribute 'autoeventwireup' is not allowed in this page. ---> System.Web.HttpException (0x80004005): The attribute 'autoeventwireup' is not allowed in this page.
    at System.Web.UI.TemplateParser.ProcessError(String message)
    at System.Web.UI.TemplateParser.OnFoundAttributeRequiringCompilation(String attribName)
    at System.Web.UI.TemplateControlParser.ProcessMainDirectiveAttribute(String deviceName, String name, String value, IDictionary parseData)
    at System.Web.UI.TemplateParser.ProcessMainDirective(IDictionary mainDirective)
    at System.Web.UI.TemplateParser.ProcessException(Exception ex)
    at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding)
    at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding)
    at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding)
    at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath)
    at System.Web.UI.TemplateParser.ParseInternal()
    at System.Web.UI.TemplateParser.Parse()
    at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType()
    at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider)
    at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders()
    at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
    at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath)
    at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
    at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
    at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound)
    at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp)
    at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
    at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    0 comments No comments

  2. Baker Kong-MSFT 3,801 Reputation points
    2020-09-15T01:48:49.13+00:00

    Hi @Vincent Jourdain ,

    The master page might be changed. Can you take a reference of below similar thread?

    Best Regards,
    Baker Kong


    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  3. Tommy Reynolds 1 Reputation point
    2020-09-15T17:36:06.087+00:00

    We're experiencing the same issue after installing September 2020 CU on a SharePoint 2016 farm. The sites use very customized master pages and home pages. Resetting to site definition is not an option.

    0 comments No comments

  4. Renato Ruben Dias (P) 1 Reputation point
    2020-09-16T09:57:40.317+00:00

    We have the same issue after installing the security updates for SharePoint 2013 that came out on windows update.

    0 comments No comments

  5. Marco Broere 6 Reputation points
    2020-09-16T20:21:18.907+00:00

    Same problem here. Seems like this occured after installing the updates. What are the KB's you guys see?
    I have KB4484488, KB4484525, KB4484515, KB4577038, KB4577048
    Message I have:
    Getting Error Message for Exception System.Web.HttpParseException (0x80004005): The referenced file '/_layouts/ep/EPSecurityControl.ascx' is not allowed on this page. ---> System.Web.HttpParseException (0x80004005): The referenced file '/_layouts/ep/EPSecurityControl.ascx' is not allowed on this page. ---> System.Web.HttpException (0x80004005): The referenced file '/_layouts/ep/EPSecurityControl.ascx' is not allowed on this page. at System.Web.UI.BaseTemplateParser.GetReferencedType(VirtualPath virtualPath, Boolean allowNoCompile) at System.Web.UI.BaseTemplateParser.GetUserControlType(VirtualPath virtualPath) at System.Web.UI.MainTagNameToTypeMapper.ProcessUserControlRegistration(UserControlRegisterEntry ucRegisterEntry) at System.Web.UI.BaseTemplateParser.ProcessDirective(... e4e2799f-611f-d0b0-9775-d61afeba893c

    I tried rebooting the server. Rebooting IIS. Updating using SharePoint Products Configuration Tool. Browsing the C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS.
    Databases have status no action required. Upgrade status is succeeded.

    I do see some messages in the Update and Migration menu. But I believe these were already there.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.