I use a Apache server as frontend balancer. So I also pass requests to a SQL Server Report Server.
The main URL is SSL secured, so the ProxyPass through the RS works with basic auth.
The report server has a interesting issue. Most of the links in the report server seems to be hardcoded http://. With that issue, many links you click on the /reports URL gives you a "Bad Request (Invalid Hostname)" from the Apache front end server.
You can browse reports, you can open them, but if you click e.g. the root link on top or the view details link to switch the list mode, then the report server uses http://yourserver/reports/... which results in an error. Correct links are https:// in this setup.
Link which are not http:// hardcoded works so far.
I opened a support ticket at Microsoft already which escalated to redmond to the dev team. The result was... this is by design and can't be changed. Is MS really so censored? Anyway. Did anyone face the same situation and got a workaround to fix that?
I am not that familiar with Apache config, but maybe is there a way to do a URL rewrite within the Apache? So if the Apache gets an http://myfrontendurl/reports/... it replaces the request with https:// ?
I'd recommend deactivating the http access from the Reporting Services Configuration tool and seeing what happens.
Related
I have a dashboard built with PowerBI Desktop. This dashboard has 3 differents data sources (SQL Server, CSV and API). I have a PRO account.
Everything works fine, but when I want to connect it with my gateway after pubication, it raise me an error for SQL Server connection:
Sorry, it's in french, but it says "Cannot update this datasource credentials. Unknown error"...
What I tried so far:
Fully reconfigure the gateway
Tryed to connect with different credentials
Updated datasources authentification methods (from desktop) and
publish it again
Publish my dashboard on different workspace
Of course, my credentials works fine in my SQL Server
I run out of idea... and I really need to setup this in order to make scheduled refresh.
I have a subsidiary question: there is any good practice about credentials to use right here? It is better to use a service account or personal account for this kind of connection ?
Many thank's for your help.
I have set up a new SSRS 2019 site with HTTPS & DNS. When I am connecting to the site through the https://ComputerFQDN/Reports then everything works just fine. When I try to connect through DNS to https://DNSName/Reports then the main page comes up and everything functions, until I try to run a report and then I get a 404 error. I can't figure out what setting I am missing or why all the reports work with the FQDN but fail with DNS alias.
Certificate is good and has the FQDN + DNS entries.
Tried with multiple DNS entries and get the same error.
Tried multiple browsers with same results and multiple computers.
I have checked that the DNS entries are both in the URL ACL and the RSReportServer.config files.
Server is configured to only use HTTPS.
Server is not running IIS.
This is an on-prem install and not in the cloud.
SQL 2019 with an Always On High Availability cluster.
I've read everything I can find, but so far I have not been able to find an answer to this problem.
Problem resolved. The DNS entries were not properly input into the URLACL for ReportServer.
When looking at the "netsh http show urlacl" command we noticed that the /Reports entries were present for the DNS entries, but were not present for the /ReportServer entry. Once we added the entries for the /ReportServer then it started working correctly.
I am using Tomcat 8.0.45 to deploy java based web application. I am using IIS 8.5 and BonCode connector. The App uses MS SQL db located on different server and IIS on another. Both are not on the same machine.
Issue:
- I followed steps for integratedSecurity=true, then copying sqljdbc_auth.dll in jre/bin.
- I also followed the steps to configure tag inside web.config along with userName (AD user) and password.
- I also mapped the user (AD user ) to SQL server db.
- But still I am not able to make it work. On Tomcat startup, I get error.
"Login failed for User 'MyDomain\ServerName$. ClientConnectionId:3b1161.....'.
My above steps could not wrong or incomplete. I can share logs but the above error is what I get in log file.
Can some one please direct me to any link or provide help here. Please note that mine in java based web app. I found lot of examples but they were all dot net based.
Thanks in advance.
We're using SSRS 2016 & SQL SERVER 2016 in our environment and don't want to use IIS. We've a requirement to re-direct report manager URL to Target URL (Similar to URL rewrite function of IIS).
For example:
http://ssrs01/pages/redirect.aspx?redirectnewurl
When someone access above URL they should be automatically routed to - "redirectnewurl"
I did research a lot and found this link useful which redirects from http: to https:
https://www.experts-exchange.com/questions/26319133/SSRS-2008-R2-How-to-redirect-URL-from-http-to-https-when-IIS-not-installed.html
But we don't have any need to use SSL as it is only internal environment and looking for any other optimal solution by changing web.config file in my reporting server
After successfully installing SQL Server Express 2012. I am trying to get set up my Report Builder. Unfortunately I am asked for a password when clicking on the Report manager URL or the Web Services URL. It says something like this (connecting to "my_Pc").
As far as I am aware I do not have any password on my PC nor set up one when configuring my SQL Server. Please note that I have not configure SSRS yet and my Service account is still ReportServer$SQLExpress. How do I sort this out please
?
Issue is with how you have created data source for Report.
Data source is created with option "Prompted Credentials" .
It should be created with "Stored Credentials" or "Windows Integrated Security"
Read more
At one point you might have configured the user "sa", have you tried using sa login to access the report page? If you are using machine id to authenticate with sql server, to configure a new user, after you connect to your database, browse down to security > logins > right-click and choose "new login".
One easy solution for this is to check the browser you are using . |I was using internet explorer edge and realise that explorer edge was simply not trusting that site. So if you are on explorer just go on setting and trust the site.
However I was on IE edge which does not trust any site. I changed it for google chrome. Everything is running perfectly fine. just change the browser (Internet Explorer best as Google could pose problem to visualize data when creating reports) and refresh everything should be running just fine.