Could not load type ‘Microsoft.AnalysisServices.SharePoint.Integration.ReportGalleryView’

A number of people have hit this issue and so it deserves a quick walkthrough of why it (unfortunately) can happen and how you fix it.

The error occurs when you try to select a Document Library of type PowerPivot Gallery (sometimes referred to as Report Gallery). After installing Power Pivot for SharePoint, all new site collections you create have the option to create a new document library of this type and if you use the PowerPivot Site template when creating the site collection, we automatically add a library of this type (that is the main thing we do in this template). The ability to add this type of library in all new site collections is there because we defined the library in a feature which is subsequently stapled to all sites. This means it is automatically activated on all site collections. The problem is that the page which is loaded when you click on the library as its default view uses an ASP.Net control whose code behind is found in a dll which is not being found. So when does this happen. Every case I have seen so far, this occurs when the user creates a new Web Application and does not deploy our WebApp solution to the new Web Application. Because of how we reference the classes for our pages, we need to have the associated assembly in the <vdir>\bin directory. This assembly is Microsoft.AnalysisServices.SharePoint.Integration.dll. The dll is “pushed” to the web applications on every WFE in the farm via the SharePoint solution infrastructure.

Ignoring any of the questions around “how should we have done this to avoid this error” .. to fix this situation, you simply need to deploy our web app solution to the Web Application you just created. To do this, go first to the System Settings page in Central Admin

Under Farm Management, select Manage farm solutions.

Click on the powerpivotwebapp.wsp solution to see its properties

On the properties page, you will see the “Deployed To” list and notice that your new web application is not on this list. Select the “Deploy Solution” link at the top of this page

You can now chose to deploy our solution to the new Web Application you have created (and you can chose to do it “Now”). After this, the bits will be pushed to all machines in the farm and you can use the PowerPivot Gallery in your new site collections.  One thing to note (since I got burned by this) … instinct is, after this is done, to just go back to the error page and hit refresh thinking that it should be fixed now. The error page, though, is an actual error page and when you hit refresh, all you are doing is reloading the error page. To actually reload the PowerPivot Gallery, use the back button in your browser or click on the “Go back to site” link in the error page.

Configure a stand-alone deployment (single server deployment)

• .From the Start menu, run Microsoft FAST Search Server 2010 for SharePoint Configuration Wizard as a local administrator.
• On the Welcome page, click Next.
• On the Select the deployment type page, select Single server (stand-alone) and then click Next.
• On the Enter the user name and password page, enter the user name and password for the FAST Search Server 2010 for SharePoint user. This user must be a domain user. Refer to Required permissions for more information.
• On the Enter a certificate password page, enter a certificate password of your choice. This password will be used to protect the general purpose FAST Search certificate. You will need this password to install certificates on other servers. Retype the password and then click Next.
• On the Server settings page, enter the fully qualified domain name of the server and the base port. A deployment file will be generated automatically with all the settings configured.

Note: 
If you require a specific setup, you can create and use a custom deployment file. If you want to do this, select Use an existing deployment file, and then enter the Deployment file location. Refer to deployment.xml reference for more information.

• On the Database settings page, enter connection information to the SQL database that you installed and created before you installed FAST Search Server 2010 for SharePoint. Enter the Database connection string in the format <ServerName>\<DBInstanceName> (Example: mysqlserver1.test.com\myinstance).
  
  To determine the database connection string: On the server where the SQL Server is installed, open SQL Server Configuration Manager from the Start menu. Under SQL Server Services, you see the SQL Server main service. The service name contains the connection string in parentheses.
  
  Enter the Database name and Database port. The database will be created when you complete the configuration wizard. Click Next.
• On the Click-through relevancy settings page, add the desired relevancy click-through settings. Click-through relevancy enables automatic relevancy tuning based on how search users click on results. Select the relevant Microsoft SharePoint Server 2010 installation type.
• If you have installed SharePoint Server 2010 using the Standalone option, specify the Fully Qualified Domain Name (FQDN) of the SharePoint Server 2010.
• If you have installed SharePoint Server 2010 using the Server Farm option, specify the user who is running the Microsoft SharePoint 2010 Timer Service. This user is specified in the SharePoint Server 2010 post-setup configuration.
• If you do not want click-through relevancy, or if you do not have the necessary information, select Do not enable click-through relevancy.

Click Next.

• On the Configuration settings summary page, review the settings and then click Configure.
  
  Wait while the configuration finishes.
• On the Post-setup configuration was successful page, click Finish.

Note: 
If configuration was unsuccessful, a failure page will appear with a link to the relevant log file.

• Before you restart the server, make sure that administrative permissions are defined. Update the local FASTSearchAdministrators group (which was created by the configuration wizard) to include either the user who will administer the FAST Search Server 2010 for SharePoint farm, or the domain group of your FAST Search Administrators.
• Restart the server.

Verify that all modules are running

• Log in as a user who is a member of the local FASTSearchAdministrators group.
• On the Start menu, click All Programs.
• Click Microsoft FAST Search Server 2010 for SharePoint.
• Right-click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator.
• At the Windows PowerShell command prompt, type the following command:
  nctrl status
• Make sure that all modules have the status Running.

Missing People Results in SharePoint 2010

Real quick, I wanted to share with you what I did to remedy this situation.  I’m sure they’ll have this fixed by RTM, so don’t worry if it’s not perfect:

• Open your Search site in SharePoint Designer 2010.  The URL will be something like http://sitename.test.com/Search
• Click All Files on the left side of the screen.
• Copy the Results.aspx page, and paste a copy right there in the same folder.  Rename the copy to peopleresults.aspx.
• Browse to your new page in the browser.  Click the <Page> tab at the top, and click <Edit> at the top left to edit the page.
• On the left side of the page, delete the “Refinement” web part, and replace it with the “People Refinement” web part. 
  Note that all of the Search web parts are grouped together under Search in the list of web parts to insert.
• Delete the Search Core Results web part, and replace it with the People Search Core Results one.
• In the top zone, replace the Search Box with the People Search Box. Done editing.
• I’ve also noticed that when I’m looking at tag profiles in SharePoint 2010, there’s a button in each tag page that says “View people who are following this tag”.  Notice that the URL for this link is under http://sitename.test.com/Search/Pages/Peopleresults.aspx.  This page needs to be created also.
• In SharePoint Designer, in All Files, right click and create a new folder.  Call this folder Pages.
• Copy the peopleresults.aspx file you just perfected AND the results.aspx, navigate to the new Pages folder, and simply paste them in there.

Again, maybe I’m missing something in the bigger picture as to why these pages didn’t exist, but this was just a little bug I came across today, and quickly fixed.  Enjoy.