Saturday, November 16, 2013
Code blocks are not allowed in this file + Performance Point
What is performance point service (PPS)?
PerformancePoint Services is a that you can use to monitor and analyze your business. By providing flexible, easy-to-use tools for building dashboards, scorecards, reports, and key performance (KPIs), PerformancePoint Services can help everyone across an organization make informed business decisions that align with companywide objectives and strategy.
Functionality: Scorecards, dashboards, and KPIs help drive accountability. Integrated analytics help employees move quickly from monitoring information to analyzing it and, when appropriate, sharing it throughout the organization.
One of our users raised a ticket by mentioning “facing problem while using performance point service w.r.t. BI dashboards. Further probing reflected the fact that he was using site with BI template with PPS activated features.
So far so good but while opening PPSSample.aspx, he was getting the following error message- i.e.
An error occurred during the processing of /PerformancePoint/Pages/ppssample.aspx. Code blocks are not allowed in this file.
Further checks provided that ppssample.aspx page is by-default one and not a customized. You will find this under every web application’s site collection. Previously I thought it might be web application specific but I was able to reproduce it across all web apps so it’s a farm wide issue.
One thing we need to understand that there is nothing wrong in your activated features or enabled performance point functionality. Also, not all the users use PPS functionality so you need to take the decision very carefully w.r.t. following troubleshooting.
(neat and simple)- 2 step resolution:
Placed this in the web.config file of the web application within the
That’s it- Your issue will be resolved.
Note: I mentioned about decision (refer the underlined keyword) - here is the fact- Thanks to Justin Kobel’s article who have stated- “the page parser ” both open up a huge security hole within the page (allowing server side code to be authored within SPD and executed within your page), as well as causing issues in a farm scenario (trying to keep all of your web.config’s in sync, causing recovery issues, etc.)
So the alternate solution which is little bit tricky and need SPD.
Here are the references:
If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, .
Product applies to-
-SharePoint Server 2010
-SharePoint Foundation 2010
-SharePoint Server 2013
-SharePoint Foundation 2013
Location: Birmingham, West Midlands, UK