Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Woke up this morning to this error out of EP:
I'm not sure what the problem here is.
Did you try doing an IISRESET on the SharePoint server? Can you also check the event viewer on the server for any more details?
We tried IISRESET, but it didn't work.
Here is a more detailed error:
I will check the error log as well.
Here is the event log warning:
Event code: 3006
Event message: A parser error has occurred.
Event time: 10/6/2020 8:18:51 AM
Event time (UTC): 10/6/2020 3:18:51 PM
Event ID: 7b002b4d3214482e96854985810d02d2
Event sequence: 34
Event occurrence: 5
Event detail code: 0
Application domain: /LM/W3SVC/85053772/ROOT-1-132464707881381399
Trust level: Full
Application Virtual Path: /
Application Path: C:\inetpub\wwwroot\wss\VirtualDirectories\80\
Machine name: VR00SP201406A59
Process ID: 3700
Process name: w3wp.exe
Account name: myDomain\businessconnectoraccount
Exception type: HttpParseException
Exception message: The referenced file '/_layouts/ep/EPSecurityControl.ascx' is not allowed on this page.
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.ParseFile(String physicalPath, VirtualPath virtualPath)
at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider)
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.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
The referenced file '/_layouts/ep/EPSecurityControl.ascx' is not allowed on this page.
at System.Web.UI.TemplateParser.ProcessError(String message)
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(String directiveName, IDictionary directive)
Request URL: myEP.com:443/.../default.aspx
Request path: /sites/DynamicsAx/default.aspx
User host address: 10.0.0.163
Is authenticated: True
Authentication Type: Federation
Thread account name: myDomain\businessconnectoraccount
Thread ID: 26
Thread account name: myDomain\businessconnectoraccount
Is impersonating: False
Stack trace: at System.Web.UI.TemplateParser.ProcessException(Exception ex)
Custom event details:
Will it be possible for you to restart Sharepoint services and check if that takes care of the issue?
It's a caching issue that we have seen before. Mostly we used to restart the server hosting SharePoint.
Hi bRradlyJames ,
Did you recently install any security updates for Sharepoint? If so then this might be the reason:
In sharepoint september 2020 Cu, new security rules were added :“allowServerSideScript=false” & “allowUnsafeControls=false” , It affects Sharepoint 2019 , 2016 , 2013 & 2010.
more info: support.microsoft.com/.../security-update-for-sharepoint-foundation-2010-sept-8-2020
Funny you bring that up. I just checked a few minutes before your comment and a bunch of security updates came through yesterday. I'll have to uninstall those...?
Try this :
In SharePoint web.config, find <SafeMode> tag
Add this entry
<PageParserPath VirtualPath="/*" CompilationMode="Always" AllowServerSideScript="true" AllowUnsafeControls="true" IncludeSubFolders="true"></PageParserPath>
you will have something like this:
<SafeMode ControlCompatMode="true" MaxControls="200" CallStack="false" DirectFileDependencies="10" TotalFileDependencies="250" AllowPageLevelTrace="false"><PageParserPaths><PageParserPath VirtualPath="/*" CompilationMode="Always" AllowServerSideScript="true" AllowUnsafeControls="true" IncludeSubFolders="true"></PageParserPath></PageParserPaths></SafeMode>
Hope this fixes your problem
That did it! You are a life saver! We are back up and running! Thank you SOOOO much!
You're welcome, glad this fixed your problem.
Hi Andre Ghazaleh,
Is it safe and recommended method?
Hi Khurshid Wali,
As I mentioned above in sharepoint september 2020 Cu, new security rules were enforced, “allowServerSideScript=false” & “allowUnsafeControls=false” are one of them.
The enforcement of these rules imposed new security requirements on 1st & 3rd party solutions that integrate with Sharepoint.
1st party affected products include Microsoft Identity Manager & MS Dynamics AX
So you either have to "uninstall" the update and loose all the added security in this update or just remove the enforcement of these 2 rules.
Today I noticed that all the Reports which I run on web controls are not working. They are not even throwing any error.
Is it also due to the recent update? Because I can run these reports from AX.
It keeps loading for infinite.
Hi Khurshid wali,
The update will cause some ghosted pages in Microsoft SharePoint not to render ,so your web controls reports will fail to render.
Did you add the PageParserPath entry? It should whitelist all controls.
Yes, I have added PageParserPath Entry. Reports are still not working on my test server.
Now I want to remove these update and test. How to Uninstall these Sharepoint Foundation updates?
there is no uninstall option for sharepoint security updates. I am using Windows Server 2012 R2 Standard
I will update here after uninstalling these updates.
It's not a simple task to "Uninstall" a Sharepoint CU , it's not just about clicking an uninstall button. I don't recommend you do it in a production environment, because a SharePoint CU updates the SharePoint files on SharePoint servers and the schemas and configuration of the databases. So to "uninstall" the CU you have to deal with both. If you don't have a backup of your DBs and checkpoints of your VMs state before the update this is gonna be a risky and tedious task.
For the future don't install Sharepoint updates directly to your production before testing it in a test environment , and don't install the update if you don't know exactly the changes it will make to your system.
Now back to your problem, if you whitelisted the web controls , the reports should work. And your problem might be caused by something other than the CU.
Check your Event Viewer to diagnose the issue before taking any actions especially if this is a production environment, also try to install the update in a test VM and see if you get same problem and if you do try to solve it first there.
I have fixed this issue through Andre Ghazaleh verified answer.
But my SSRS report issue is still there.
Solution: I haven't upgraded my client's production environment.
Business Applications communities