Verify that OAuth is configured correctly for the Machine Translation Service application proxy in SharePoint 2013

So I have just installed SharePoint 2013 SP1 and the Health Analyzer showed up this error.

Resolution: Ensure that every Web application with a Machine Translation Service application proxy has a connection to a User Profile service application and an App Management service application, and is in claims-based authentication mode.

• Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
• On the Central Administration website, click Application Management.
• On the Application Management page, in the Service Applications section, click Configure service application associations.
• In the Application Proxy Group column, click the proxy group for the Web application or service application that you want to configure. Usually it is the default Application Proxy Group.
• Select the User Profile Service Application Proxy check box and the App Management Service Application Proxy check box.
• Go back to the Central Administration Home page. In the Application Management section, click Manage web applications.
• Click the Web application you want to configure, and then click the Authentication Providers button on the ribbon.
• Ensure that the Membership Provider Name for the Default zone is Claims Based Authentication. If not, you have to migrate the Web applications from classic mode to claims-based authentication. For more information, see Migrate from classic-mode to claims-based authentication in SharePoint 2013.

The Machine Translation Service is not running when it should be running (SharePoint 2013)

So I just installed SharePoint 2013 SP1 and got this error, here is how to solve this.

• Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
• On the Central Administration website, click Monitoring.
• On the Job Definitions page, in the list of timer jobs, click Machine Translation Service Timer Job.
• On the Edit Timer Job page, in the Recurring Schedule section, specify when you want the timer job to run, and then click Enable.

Error!!! Could not load file or assembly

When you get this error like I did, and it tells you the assembly file version or error says The located assembly's manifest definition does not match the assembly reference.

you'll have to follow the steps to get the dll files from windows assembly GAC
my example is about the ReportViewer.ProcessingObjectModel version so I'll use this. However you can use whatever is missing dll in your error

Open a command prompt in Administrator mode

Type cd \windows\assembly\gac_msil\Microsoft.ReportViewer.ProcessingObjectModel press Enter

Type dir so it lists the files/folders inside and press Enter and check your required version folder is available

in my case my required version was 11.0.0.0__89845dcd8080cc91 so I typed cd 11.0.0.0__89845dcd8080cc91 and press Enter

you'll be able to find Microsoft.ReportViewer.ProcessingObjectModel.dll in this folder

now we will copy this dll type command copy*.dll c:\dll (or any folder you wish to copy) and press Enter

now the dll is copied to your specified folder and you can use it as a reference in your project folder.

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, it automatically adds 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 the WebApp solution to the new Web Application. Because of how MS 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 the 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 the 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.

SSRS 2008 Tablix control Repeat Column Headers does not work

If you faced the issue which I have faced, that you created your nice looking report, and next thing you realise the Column headers do not repeat, no matter what you did was not good enough to fix it.

Here is the solution:

Select the Tablix that you want to repeat column headers for by clicking on it.

At the bottom of the screen, find the "Row Groups" and "Column Groups" section.

Click the small drop-down-arrow on the right side of that section, and select the Advanced Mode.

Now you'll see additional lines called (static) in rows and columns groups.

In the "Row Groups" section, locate the top-outermost "static" row and click on it.

In the properties pane, you need to set the following properties:

KeepTogether = True
KeepWithGroup = After
RepeatOnNewPage = True

All of these properties must be set for this to work properly.

Good luck!

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.