Edit URL Link to Report Server within SSRS Subscription - reporting-services

I recently upgraded from SSRS Report Server 2008 to Power BI Report Server 2017. I have set up an alias URL link to get to the server as well.
When sending a report from the new server via an email Subscription, there is an option to send a link to the reportserver along with it. When using the new reportserver, the link does not use the reportserver alias to link to the server. It instead uses the machine name of the SSRS server itself.
Example: http://machinename/reports/reportname
Instead of: http://reportserveralias.example.com/reports/reportname
I did find microsft's link that describes a URLRoot properly in the rsreportserver.config file. Here is a link to Microsoft's website that describes the file's capabilities.
https://learn.microsoft.com/en-us/sql/reporting-services/report-server/rsreportserver-config-configuration-file?view=sql-server-2017
I tried editing it, but to no avail. I also tried restarting the reporting service afterward and that did not work.
May anyone please help me with this?
Thanks!

You indeed have to configure the UrlRoot in the RSReportServer.config file, but it must not point to the Web Portal but to the Web Service. In most cases, the virtual directory is named "reportserver" (verify this in Reporting Services Configuration Manager under Webservice URL).
The configuration option in the RSReportServer.config file is found under
<Configuration>
...
<Service>
...
and in your scenario it should look like this:
<UrlRoot>http://reportserveralias.example.com/reportserver</UrlRoot>
As an additional suggestion, bind the webservice and webportal URLs to an SSL certificate (issued for reportserveralias.example.com or *.example.com) and use https instead.

Related

SSRS Configuration Error; Invalid PBI Configuration

I got this issue on one of my machines when I installed MSSQL Server 2016 with SSIS, SSAS and SSRS.
SSIS and SSAS is working fine but SSRS does not.
After the installation, I opened the Reporting Services Configuration Manager and leave everything to default. This usually the end of it, but for some reason when opening the Portal, I got this:
When I check the log, the error is
ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: Invalid PBI Configuration, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
What is Invalid PBI Configuration? And how do I identify the problem?
Thank you in advance.
Took a while to sort this out, but it's a simple fix.
Open SQL Server Reporting Services Configuration Manager
Click on Web Service URL menu and make sure that the URL's match the ones located in Web Portal URL menu.
If they're different, open the rsreportserver.config file (C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer) and remove any entries not listed in Web Service URL.
Open your web portal ie. http://localhost/Reports and see if it's resolved. If so, all done.
If not, click the Encryption Keys menu, in the "Delete Encrypted Content" section, click "Delete".
Open your web portal again and see if it's resolved.
Locate and update your datasource credentials.

SQL Server Reporting Services - cannot authenticate through URL on the same machine as SSRS server

I am accessing SSRS reports (SQL Server 2016) through URL to embed them in my application in an iFrame. When I access SSRS reports remotely, i.e from different computer I can authenticate and display the reports.
In my iFrame source I put:
http://example.com:4000/path_to_ReportServer/report_name
And that works fine when I deploy my app to stage server. All the SSRS reports load with no problem at all.
However I develop on the same PC as my SSRS report server resides, and when I am on it I have to change all the links in iFrames to:
http://computername:4000/path_to_ReportServer/report_name
edit: originally I wrote here that I use localhost, but actual I meant computer name.
If I try to run my app from VS on my dev machine and I do not change the domain to computer name I wont be able to authenticate at all. It just keeps asking me for the same credentials over and over again.
I've checked the ReportServerService log, and I see this as a last line when I try to log in:
library!DefaultDomain!3bd0!11/21/2016-12:52:36:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: Invalid PBI Configuration, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
I looked for this problem extensively, and I only find MS configuration tutorial but no one having similar issue to mine.
I have checked the usual culprits like firewall or port conflicts (but if I had any of those I would not be able to access the SSRS from any other PC, yet I can and the link doesn't work only on local machine.)
I am very new to SSRS in general so please kindly be patient with me. Thanks!
A few things you can try:
In SSRS Configuration and ensure that the Report Service and Report Management endpoints are valid (Copy the url in the hyperlink and make sure it opens on your local host.)
In SSRS Configuration and ensure that the Report Service Database has been properly deployed.
Remove any custom modules/assemblies you have applied to the default behavior from the ssrs web config (Custom Security).
I think you have applied changes to ssrs's web config in order to have it load assemblies for your custom security, custom datasourse/dataset, custom render format and fat fingered the config somehow.
You're probably running into a same-origin-policy error, which wikipedia states as under the policy, a web browser permits scripts contained in a first web page to access data in a second web page, but only if both web pages have the same origin.
The fix is to implement the X-Frame-Options metatag, like so:
X-Frame-Options: ALLOW-FROM https://example.com/

Error: The specified TargetServerURL is not valid. Specify a valid URL for report server in the deployment settings

I have created a Report Server Project in Visual Studio 2013. The actual report server was a pre-existing server whose reports were previously populated via the Report Builder tool. I have downloaded the .RDL files locally and added them to the project under the /Reports folder.
When I try to deploy the reports I am receiving the 'TargetServerURL' is not valid error. I have researched the answers here and here.
I can successfully navigate to http:///Reports_PRODUCTION which displays the reports, and also to http:///ReportServer_PRODUCTION which offers an FTP-view of the report structure.
In the project properties I have set the 'TargetServerURL' to both of these URLs and neither has worked. I've verified that the target server version is correctly set - SQL Server 2008 R2. Am I missing something?
Thanks
I found out something, so that's why I post to this old question.
I had the same problems after starting a new VS2013 SSRS project and tried to deploy to the same RS server, but to a different server.
I kept getting the error: The specified TargetServerURL is not valid. Specify a valid URL for report server in the deployment settings.
After quadruple checking everything,I found that I was changing the ssrs project property on Release mode but in VS 2013 I was deploying the project in Debug mode. After changing the VS 2013 configuration to run as Release it found the right ssrs project settings and deployed fine on first run.
I read these answers and looked in my Configuration Manager (Right click project name > Properties > Configuration Manager > and picked the Server that was configured. It shows up checked like the image. I had been uploading with correct info, just didn't have the configuration fully done on my new project which used files and locations from older project:
Screenshot of Configuration Manager and Settings
I would start by looking at what SSRS thinks the service endpoint is and I bet that is the one you should be using.
Open the Sql Server 20XX Reporting Service Configuration Manager.
NOTE : This is found under the Sql Server progam group and maybe in a subfolder.
Select the service instance you want to connect to and click Connect
Navigate to the "Web Service Url" Tree List View Item in the list on the left hand side of the window.
Note the URLs: value in the "Report Server Web Service URLs" group box at the bottom of the Web Service URL panel. (This is the url you should use to connect with)
NOTE : If this is on a remote server then you will need to http or https to the domain in place of localhost or machine name if that is how the Report service was set up. If you can not access https:\\MACHINENAME/SSRS from your local machine then simply replace the url with https:\\www.mymachinenameurl.com/SSRS
make sure your deployment settings for the configuration you are deploying from are set (deploying in debug, ensure you are referring to debug deployment settings)
trust me I've been there .. Allot
I reached here because I've had the same error, and I was not able to deploy my report .
Anyways, at some point I tried to deploy the report manually by uploading to the library that I've already prepared with the Reporting Content Types, but the datasource was appearing as unknown file types, and couldn't access Manage Data Sources of the report.
tried to run the report hopelessly and noticed the url
http://ServerName/PWA/_layouts/15/ReportServer/RSViewerPage.aspx?rv:RelativeReportUrl=/PWA/Reports%20Library/Weekly%20Status%20Report.rdl
I tried to use the url http://ServerName/PWA/_layouts/15/ReportServer as "TargetServerURL" and it worked
for the other properties like the Datasets, reports ... I used the following urls
Report: http://ServerName/PWA/Reports%20Library/
DataSets: http://ServerName/PWA/Reports%20Library/Datasets
datasource: http://ServerName/PWA/Reports%20Library/datasource
and this was the end of my suffer and was able to deploy correctly and manage every property of the report, datasets, and datasources

Deploy rdl report to remote server

I have report solution file with one project and one report.I have designed rdl report using BI in SSDT tools. After creating report successfully build is success and preview is ok. No problem did not arise when i did create report.
Now, I want to deploy this report to my remote reporting server. I gave a url like this www.plumeria.arvixe.com/Reports into Target server url. when i press deploy then need username and password, i gave that. after certain time it appears a errors like this.
Many times i have tried but not get a proper solution step by step deploy rdl report to remote server.
Is there any solution? Thanks.
"like this www.plumeria.arvixe.com/Reports into Target server url" is not correct. What you are referring to is the Report Manager.
You have to correctly specify:
Target Dataset folder
Target Data Source Folder
Target Report Folder -->From your project
Target Server URL-->Get it from Reporting Services Configuration Manager
Target Server version.
You may need elevvated permissions in SSDT.
My target url used in my book is as follows:
http://HODENTEKWIN7/Report_Server_Kailua
The instance name of SQL Server is Kailua and it is native mode.
This is a comprehensive book covering SQL Server 2012 both native mode and SharePoint

How to configure the URL of generated reports in e-mail subscription of Reporting Services?

I have Reporting Services 2005 running on a machine that I can access only through Internet by typing http://[server ip]/Reports. This works fine, but my problem is:
Go to a report and click Subscriptions
Select Delivered by E-mail
Check "Include link"
Create a schedule
At the specified time, I do receive the e-mail but the link to the report comes in the format http://[host name]/reportserver[...]. Clicking this link does not work because my pc can't resolve hostname.
How can I configure this link for Internet access? I mean, I want the link to be http://[server ip]/reportserver[...].
Thanks in advance.
Look in the RSReportServer.config on the server file for URLRoot configuration setting. See the 2005 version of the documentation. The SSRS config files were changed and merged in SSRS 2008, so use the docs for the right version.