Wednesday, July 31, 2013

SharePoint 2013 PerformancePoint CodeBlocks Not Allowed followed by PerformancePoint designer stopped working Error Code: clr20r2

When moving a BI Site collection from server to server using backup and restore of the site 9/10 times PerformancePoint doesn't work.

The 2 basic steps below usually work for me

1- Go to the web.config file of the web application within the <PageParserPath> header add the following line.
<PageParserPath VirtualPath="<insert PPSSample Path Here>" CompilationMode="Always" AllowServerSideScript="true" />
IISReset /noforce

The default path for the ppssample aspx is probably /Pages/ppssample.aspx
if after fooling around with the above script PerformancePoint still gives you the codeblocks are not allowed error try the below to get it working for debugging purposes but this is a security concern if used especially on production
<PageParserPath VirtualPath="/*" CompilationMode="Always" AllowServerSideScript="true" />

Now sometimes when this error has been resolved PerformancePoint decides to throw another error stating the below
PerformancePoint designer stopped working Error Code: clr20r2 
This happens especially frequently if you have been using PerformancePoint on this machine before restoring this site because the cache contains incorrect references. To solve this issue we go to step 2

2- 
Go to C:\Users\<CurrentLoggedInUser>\AppData\Local\Apps\2.0
Delete all the files and folder in this path
Try to start PerformancePoint now and it should work


Monday, May 27, 2013

Upgrading to SharePoint 2013 and SQL Server 2012

After deciding to take the leap of faith I considered my options as to what the safest way to upgrading my SharePoint site collection to SharePoint 2013 and upgrading my SSAS Database to SQL Server 2012.

I decided to create a new machine that had SharePoint 2013 and SQL Server 2012 fresh installations and to attempt to migrate my solution manually without the upgrade wizard.

this was done in the following order


  1. Install SQL Server 2012 Enterprise (Database, SSAS in Multidimensional Mode, SSIS, SSRS)
  2. Install SharePoint 2013 Enterprise using the above database instance for hosting the config database
  3. Install SQL Server 2012 Enterprise PowerPivot and configure PowerPivot to create a new site collection


Most of the steps were fairly simple and straight forward. After i had a stable environment i then began to migrate my solution starting with the site

Take backup of the site's content database and use the below command to restore it to SharePoint 2013
  • Mount-SPContentDatabase "<ContentDb>" -DatabaseServer "<DbServer>" -WebApplication http://SiteName

After mounting the database upgrade it from the Central Admin. this should go pretty smoothly providing you don't have any custom code in your SharePoint site

i then proceeded to upgrade my SSIS packages and SSAS database which also went smoothly.

Then the first problem arose which is PerformancePoint could NOT connect to SSAS no matter which user i configured PerformancePoint with, after checking the logs i found this

System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.AnalysisServices.AdomdClient, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

Basically this means that PerformancePoint is still using ADOMD v10 and not v11 which comes with SQL Server 2012 to try to connect. After installing ADOMD v10 from SQL Server 2008 R2 Feature Pack everything was finally working