We are using SQL Server 2014 Reporting Services to produce reports. Recently, we have had to switch our links to https. Since that time, we are unable to access the reports from outside the local server. When accessed, we only get in return the message "The page cannot be displayed because an internal server error has occurred."
We have tried configuring the web service url for SSRS to use the SSL certificate, but that does not seem to resolve the issue. Is there a setting somewhere else that needs changed?
Related
I'm following the following thread to configure SSRS for SSL.
Configure SSRS for SSL
Here's what I have.
netsh http add urlacl url=https://dbserver.mydomain.org:443/Reportserver_Test/ user="NT Service\ReportServer$Test" listen=yes addl=S-1-5-80-3637326371-3941449338-1192580090-1447153118-1238582853
And the error is:
Url reservation add failed, Error: 87
The parameter is incorrect.
I don't know what's wrong with the command I've used; however, here's how I resolved the issue with SSL in SSRS.
I opened up the rereportserver.config file
Delete everything in the tags
Restart SQL Server Reporting Services
Open Reporting Services Configuration Manager
Re-setup Web Services URl with SSL Certificate
Click Apply
This seems to work for me for the moment.
Let me first describe the actual situation: We want to build a new SQL Server enviroment based on SQL Server 2016. AS you may know, in SQL Server 2016 the mobile reports from Datazen are integrated. So far so good. The Problem: In our current Enviroment, there is one internal Datazen Server and one external server. The external Datazen server exists only to read data from the internal one. So there is no direct Data Access (to Data Sources), the administration part is disabled and only the needed Services (to read from internal server) are installed. We want to build that same archtiecture in SQL Server 2016 Reporting Services. Do you know any way to do that?
I thought the best solution was a second SQL Server with Reporting Services but only read access on the other SQL Server (didn't found any setting like this).
We don't want the internal server to be accessible over the web beacause of security.
interesting question, but not sure i understand correctly ;) what do you mean with "the external datazen Server exists only to read data from the internal one"? How does this configuration look like? Do you have a sale out Deployment where the external Servers hosts "Web Application" and "Share Cache Instance" while internal Server hosts "Data Acquisition" and the same roles as the external Server?
In SSRS you can also Scale out web frontends, but all Servers will act as "data acquisition server" to stay in datazen terminology. Do you have security concerns with this topology? Whats the difference to have the data "read only" in DMZ or connect from DMZ/external Server to internal datasources? One Option would be to do a secure Application Publishing of internal SSRS Server with a Firewall like Microsoft ISA Server
We are planning to deploy reporting service using Microsoft Reporting Server 2012. As I understand it, there will be three components;
Database (SQL Server)
SSRS (Reporting Server)
IIS (Web front end) - SharePoint (alternate Front end)
In setting up the Proof-of-Concept, the dev installed SSRS and SQL Server on same box (let's call it the DB server) and is redirecting client browser to a URL on DB Server from web front end.
Is it possible to architect the solution so that the web front end is the only destination for client browsers, SSRS lives on its own dedicated server separate from both the Web server and the DB Server?
How will authentication work in this scenario? We are using integrated authentication using Enterprise AD.
Configurations I have used in the past are these:
SQL Server on one server; SSRS native on another server. Users accessed reports via the SSRS Report Manager web UI that comes with SSRS.
SQL Server on one server; SSRS install in SharePoint Hosting mode on another server. Users accessed reports via SharePoint.
I am not 100% sure what you mean by “web front end is the only destination for client browsers”. If you mean that the end user only hits a web server, and not the database server to get reports, then either one of the above will work. If you have an existing intranet site that you want to host reports in, you can do so via web parts, if you are using MS technologies. You will still need SSRS setup somewhere so you can deploy reports, and the web part would read from it. Or, you can continue the redirect to either Report Manager or SharePoint if you go that route.
As far as authentication: the authentication between SSRS and SQL Server is usually done via an AD (Active Directory) user/service account that SSRS runs under, and also has access to the databases is uses on the SQL Server.
The authentication that allows users to browse and execute reports is usually done via AD as well. You can add all users to a central AD group and give that group Browser permissions on the SSRS server. This authentication would still apply if you use web parts to host reports outside of SSRS Report Manager.
The authentication that SSRS uses to pull the data that ends up showing in reports is usually SQL Server authentication, or whatever authentication that your data source supports where you can send a user name and password (which is stored within a shares data source on SSRS).
More Info
I have been wanting to deploy my SSRS reports to a Test server. However I found that on that server the SSRS service had stopped, and I had to change the setting so that it used a built in Network Service account. After doing that I found I could start the service. However when I key in the ReportService url in my browser, I get the above error message.
One problem that I had when I changed the settings to the Network Service account is that I got the error message:
"A connection could not be established with the information provide. Hit OK to change your connection settings.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: named Pipes Privider, error: 40 - Could not open a connection to SQL Server)"
Even so, this did not stop the service from starting.
As a result of all this I still cannot deploy my reports. How do I fix this?
If you are running SSRS 2016, restart the SSRS services:
SQL Server Reporting Services (MSSQLSERVER)
SQL Server Reporting Services Web App (MSSQLSERVER)
The best way to find the answer is to check the log files.
You can find the log files for report server at below path:
In SQL Server Reporting Services 2016 or earlier: C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles
In SQL Server Reporting Services 2017: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles
Thanks & Regards
Karan
Error 503 Usually comes if the database credentials are wrong , you can test the connection from Reporting Configuration Manager.
Otherwise, Check the Reportserver config file "rsreportserver" at path
C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer
and find the following tags are correct or not.!
<Authentication>
<AuthenticationTypes>
<RSWindowsNTLM/>
</AuthenticationTypes>
<RSWindowsExtendedProtectionLevel>Off</RSWindowsExtendedProtectionLevel>
<RSWindowsExtendedProtectionScenario>Proxy</RSWindowsExtendedProtectionScenario>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Authentication>
According to user permissions/properties you can change <AuthenticationTypes> tag.
Restart Following Services
SQL Server Reporting Services (MSSQLSERVER)
SQL Server Reporting Services Web App (MSSQLSERVER)
This error is also generated if you are using a trial version of SSRS and it has expired.
Find <IsWebServiceEnabled>False</IsWebServiceEnabled> and change to
<IsWebServiceEnabled>True</IsWebServiceEnabled> in the rsreportserver
config file.
I was getting this error and tried deleting the URL's from the rsreportserver.config file.
After lots of frustration, I found that the permissions on that file and directory itself did not allow ReportServer user to modify the file. Once I gave the reporting user permission on the file, all was good to remove / update URL's, and returned SSRS back into service.
Try explicitly adding the user permissions to the config file.
Good luck!
In rsreportserver.config, my value was not correct. It was showing up as: http://+:80. Of course, this needs to map to the URL specified in the Report Server Configuration Manager, Web Portal URL (ie the blue URL link that was bringing me to a "not connected" browser screen). It did not, so I got Service Unavailable with a 503 (HTTP error).
The solution: edit the value/address to match the Web Portal URL.
Web Service URL -> URLs: http://MYSERVERNAME:80/Reports
rsreportserver.config -> http://MYSERVERNAME:80/Reports
Once I saved the rsreportserver.config with the edited value to match accordingly (above), I could click on the provided link in the Web Portal section of the Report Server Configuration Manager, and it brought up the SQL Server Reporting Services page. Note: I didn't need to restart anything.
Cheers!
I have just installed SQL Server 2008 including Reporting Services on Windows Server 2003. I'm having a problem though accessing the Report Manager. When the Reporting Service is first started I can access it fine but after maybe an hour when I try and access it I get an error saying: Unable to connect to the remote server.
The reporting service is still running at this point. I can connect to it through Reporting Services Configuration Manager and clicking on the Web Service URL gives a directory listing (I assume that is correct behaviour). If I stop and start the service through Reporting Services Configuration Manager then I can access Report Manager once again (although in maybe an hour I will get the same error once again).
I've installed the latest SP1 service pack. I'm using the same domain account to run all the SQL services. The report server is set to use the default ReportServer virtual directory, is set to IP address All Assigned, TCP Port 80 and no SSL certificate. The report manager is set to use the default Reports virtual directory, IP address All Assigned, TCP Port 80 and no SSL certificates.
In the log file I get an error:
Unable to connect to remote server
HTTP status code 500
An attempt was made to access a socket in a way forbidden by its access permissions.
Does anyone have any idea why this is happening? I've searched the net but haven't been able to find a solution.
It was the anti-virus software on the server that was causing the problem. After adding the pagefile.sys as an exclusion it worked fine.
configure your rs like below link :
http://technet.microsoft.com/en-us/library/bb839480(SQL.90).aspx
maybe it solve your problem.