Quantcast
Channel: SQL Server Reporting Services, Power View forum
Viewing all articles
Browse latest Browse all 10045

SSRS 2012 SharePoint 2013 integration configuration

$
0
0

Scenario:

We have SSRS 2012 SP1 installed on Windows Server 2008 R2 Enterprise in SharePoint integrated mode withSharePoint 2013 evaluation copy. Both SharePoint 2013 and SQL/SSRS 2012 are installed on same server. The SharePoint databases are hosted on SQL 2008 R2 and Reporting services database is hosted on SQL Server 2012 enterprise. We configured reporting services following all the steps here. The reporting services are bound to default app http://SharePoint:80 and running under newly created app pool "ReportingService".

The web application app pool, reporting services application pool, app pool for SharePoint web services system and farm account are running under network services. Whereas Claims to Windows token service and SharePoint server Search service are configured to run under Local System. We also created SharePoint library (let’s call it report library) and configure it to support rdl, rsds and report builder content type.

We were able to configure shared data source (pointing to different SQL server but on same domain) and configured report to use it. We were able to browse and run thereport locally. We were able to browse the reporting library URL from remote machines (same domain as well as trusted domain).  But, when tried to execute from remote machine (both same domain as well as trusted domain) SharePoint displays following error message on webpage.

The Web application at http://servername:44846/Reports/Operation Management/report name.rdl could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.

We noticed following warning logged in event viewer  when clicking report.

Event log warning:

Alternate access mappings have not been configured.  Users or services are accessing the sitehttp://servername:44846 with the URLhttp://servername:44846.  This may cause incorrect links to be stored or returned to users.  If this is expected, add the URLhttp://servername:44846 as an AAM response URL.  For more information, see:http://go.microsoft.com/fwlink/?LinkId=114854"/>

In order to modify the datasource, when we clicked from remote machine(same domain as well as trusted domain), the SharePoint displays following error message

An unexpected error occurred while connecting to the report server. Verify that the Reporting Services Service Application mapped to this web application is available OR the report server is available and configured for SharePoint Integrated mode.

Nothing is logged to eventlog. The data source is configured to use windows authenthication. The user who was configuring the access has sysadmin rights on db server where reporting services database are hosted. The user is admin on the Server and is farm administrator on SharePoint 2013.

Is this related to security (especially the accounts under which all the services are running) ?


Nehal Jain


Viewing all articles
Browse latest Browse all 10045

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>