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.
Related
I'm running SSRS 2016 on a local machine for development purposes. I've been running into this error quite frequently and spontaneously, as in I will run a report, then 3 minutes later try running the same report with the same parameters and all of a sudden my config is broken without changes. I start mucking around with the configs and eventually, seemingly spontaneously, again it will start working again. Then the cycle continues where it works for 1 hour - a few months before just breaking again.
Here is the screenshot from my Web Service URL:
The actual error message from the log is:
ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: AuthzInitializeContextFromSid: Win32 error: 1355, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
When I google that error message I get a bunch of forum posts about sending emails and email configuration but I'm not trying to send emails nor do I have any email stuff configured.
Here is the configuration I'm using under Reporting Services Configuration Manager:
Service Account:
User Another Account (My Domain Account) I've also tried every combination of built-in account which also seem to work when the server doesn't throw this error..
Web Service URL:
IP Address: All Assigned
TCP Port: 80
HTTPS Cert: N/A
HHTPS Port: {blank}
Database:
My Local SQL Server instance and Report DBs using Windows Account login
Email Settings (all default settings):
Sender Address: {blank}
Current SMTP Delivery Method: Use SMTP Server (drop down is read only cannot be changed)
SMTP Server: {blank}
Authentication: No Authentication
Execution Account:
Specify an existing Account: unchecked
Subscription Settings:
Specify a file share account: unchecked
I've also restored and changed encryption keys numerous times and deleted all Encrypted Content under the Encryption Keys Pane. I always use the same snk file for the key and same password so I know it's correct.
If there's any additional information I can provide to help, please let me know. I know this is a bit of a longshot but it's really annoying and impedes my productivity developing SSRS reports.
Thanks in advance.
Well, after more googling, half way down the first page of results I finally came across this article:
https://support.microsoft.com/en-ca/help/3171505/fix-the-service-is-not-available-error-when-you-use-ssrs-2016-portal-a
I downloaded the suggested Cumulative Update 2 for SQL Server 2016 and low and behold, my local setup is working again. Could this be just a coincidence? Absolutely. I will report back if it dies again with the same error but I'm hopeful for the time being.
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?
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.
I am getting an error when I try and upload a import an ssis project onto our server. The server only has integration and reporting services installed as the live sql server is on another server. I log onto the integration service fine but as soon as I try to right click the MSDB folder to import a package I get the error listed at the end of this question. I have added my local user account as an administrator on the server where the Integration Service is installed and I have added the administrators group to the security permissions for MsDtsServer in component services. Any help with this would be appreciated.
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
ADDITIONAL INFORMATION:
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
BUTTONS:
OK
I had this problem recently. It was a little tricky to figure out.
Here is a nice link from MSDN on how to hack, err, I mean fix it.
Configuring the Integration Services Service
"To manage packages that are stored in a named instance or a remote instance of the Database Engine, or in multiple instances of the Database Engine, you have to modify the configuration file." - MSDN
Thanks Microsoft??
To be more specific, you need to edit this file on your server:
C:\Program Files\Microsoft SQL Server\90\DTS\Binn\ MsDtsSrvr.ini.xml
Change:
<ServerName>.</ServerName>
to
<ServerName>ServerName\InstanceName</ServerName>
Save. and reboot.
Is your server set up to accept remote sql connections? Maybe check your firewall on the server to check that all the SSIS ports are allowed through, and also check in the SQL Surface Area Configuration tool to make sure all the services are set up to allow remote connections.