Monday, March 28, 2016

Report Server has encountered a SharePoint error. in SharePOint 2013

Report Server has encountered a SharePoint error. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error. ---> Microsoft.SharePoint.SPException: The user does not exist or is not unique. ---> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors in SharePOint 2013

This is error accouring because of Anonimous access to the Microsoft Reporting Services. According to the Microsoft ; Microsoft Reporting Service not supporting annonimous access for integrated mode.



So you might be wondered how you can archive this.

Option One

Simply you can dissable the Anonimous access from IIS. But this wont work if you really want anonimous access in your farm. For an Example If are hosting internet site with integration mode public reports you can not dissable the anonimous access.



Option Two

This is a smart workaround that you can do. in sharepoint reports are rendering usign aspax called RSViewerPage.aspx which is resides in 15 hive.

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\ReportServer\RSViewerPage.aspx

So there are the steps.

  • Create a New Web Application to host your public reports.
  • Copy RSViewerPage.aspx page and paste it as RSViewerPagePublic.aspx (You can use any name)
  • Open the file and register a Control Tempplate which handles the login for the Anonimous users. We are going to implement that it will auto login to a some user account for anonimous users.

In that case report server will see it is as a authenticated user and we are just using a dummy user login to represent the anonimous user.

since it is a different web application it wont conflict with your content web application user.

<%@ Register TagPrefix="RSWP" Namespace="Microsoft.ReportingServices.SharePoint.UI.WebParts" Assembly="Microsoft.ReportingServices.SharePoint.UI.WebParts,Version=,Culture=neutral,PublicKeyToken=89845dcd8080cc91" %>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="code" TagName="AutoLogin" src="~/_controltemplates/15/Code/AutoGuestLogin.ascx" %>

<%@ Import Namespace="Microsoft.SharePoint" %>
<%@ Page language="C#" Codebehind="RSViewerPage.aspx.cs" AutoEventWireup="false" Inherits="Microsoft.ReportingServices.SharePoint.UI.RSViewerPage,Microsoft.ReportingServices.SharePoint.UI.ServerPages,Version=,Culture=neutral,PublicKeyToken=89845dcd8080cc91" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "">
<html dir="<%$Resources:wss,multipages_direction_dir_value%>" runat="server" style="overflow:hidden;width:100%;height:100%">
<head runat="server" lang="<%$Resources:wss,language_value%>">

  • Creating the control templete and a web part

You need to pass your user name and password in here and make auto login.

  • that refer change the report view url to point your created aspx,

Monday, March 21, 2016

Windows Live Writer,Error,OnCatalogResult


I was failed installing Windows Live writer  in few attempts and It didn't work for me by doing several work rounds that is available in the web.


So I have ultimately switched to the OpenLive Writter that was very similar in every aspects.

You can find the open source version of your great tool by using the following link

Friday, February 12, 2016

Browser is security restricted or JavaScript is disabled accessing Visual Studio Team foundation Servers


this is a common and simple error due to Dissable of Active Scripts. You can go to internet explorer settings and

Click –> Custom Level button

and Enable in Active Scripting under Scripting


Wednesday, February 10, 2016

The URL of the item could not be resolved. The repository might be unavailable, or the crawler proxy settings are not configured. To configure the crawler proxy settings, use Search Administration page


When you debuging your Sharepoint Search you might have come a cross that there is a error in crawl log in sharepoint farm.


The URL of the item could not be resolved. The repository might be unavailable, or the crawler proxy settings are not configured. To configure the crawler proxy settings, use Search Administration page

This is because your search can not be resolved to a perticular address ;

  • most probably youy coperate proxy blocking it
  • domain name resolution is not happening inside the sharepoint crawl

Easiest way to resolve the error is

First clear any proxy settings you have specified in the search settings.


You can go to the Crawling Proxy settings and make sure you didint specify the proxy for content crawling.


Then goto each server in your farm and add the doman name entry resolution in the HOST file.



Now you can run the crawler again and you will see there are no top level erros in your crawl log.