Skip to main content

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.

Ref: https://msdn.microsoft.com/en-us/library/bb283324.aspx#Anchor_4

image

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.

image

image

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=11.0.0.0,Culture=neutral,PublicKeyToken=89845dcd8080cc91" %>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, 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=11.0.0.0,Culture=neutral,PublicKeyToken=89845dcd8080cc91" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<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,

http://data.com/_layouts/15/ReportServer/RSViewerPagePublic.aspx?rv:RelativeReportUrl=ActivityReport.rdl

Comments

Popular posts from this blog

Complete guide to Install SharePoint in a Three Server Farm using AutpSPInstaller

This article will be divided to three sections Setting up the Environment and Service Accounts Getting Ready with AutoSPInstaller Online Configuring the XML using Online Editor and Installation Setting up the Environment and Service Accounts AutoSPInstaller Online is one of a great project that facilitate Automated SharePoint installation including Sharepoint 2010, 2013 and 2016. Auto SP Installer provides a powerful way to deploy and configure a single-server development environment to multiple-server SharePoint farm. Reference: https://autospinstaller.com/ Before doing anything we will set up the environment for SharePoint three server Farm. Will name these servers as SPWFE - Share Point Front End Server SPAPP - Share Point App server SPDB - DB server Please find the reference for SharePoint minimum requirement and practices from https://docs.microsoft.com/en-us/SharePoint/install/install-sharepoint-server-2016-across-multiple-servers For the the medium segregation, we have to create...

How to Customize New Item Form to take parameters from Query String in the SharePoint 2010

In here I'm going to explain how to customize the SharePoint Item From to take parameters from Query String and set them as default values using SharePoint designer. Using this you can open a new Item From by providing parameters as query string. For an example you can customize one item Display form and taking query String Parameter from that and view New Item view for another list by providing default values using the Query String.     Steps Open the SharePoint designer and go to list and libraries and open the list that you want. Click the New and create a New Insert View by providing the name of the view.   Then created one will come to the list. then click and open the view. Then default New Item Screen will be loaded as follows. Then Delete the default list view and make that empty. You can delete the controls by selecting the area in the design view, If it fully cleared you can view the following message from the designer. Then go to SharePoint...

Motion Eye Docker compose File

Docker compose files are comes in handy when considering container orchestration. Below example shows my docker compose files and folder structure. ---- Your Folder (motioneye)   -- etc   -- lib   -- docker-compose.yaml You can run the docker compose file using docker-compose -d , and etc and lib folder will be automatically populated in the initiation. --- Below shows the content of the docker-compose.yaml file. version: '3' services:   nodered:    image: "ccrisan/motioneye:master-amd64"    container_name: motioneye    restart: always    user: root    ports:      - 8765:8765    volumes:      - "/etc/localtime:/etc/localtime:ro"      - "./etc:/etc/motioneye"      - "./lib:/var/lib/motioneye"