October 19, 2017 at 9:18 am
Hi,
We have a relatively fresh install of SSRS 2016 at SP1 CU3.
We've been able to create reports and set up subscriptions
In the past week we've lost the ability to create new data sources or add/amend report subscriptions to existing reports.
The reports run okay still. No other updates/installs have been made.
We've been through the troubleshooting steps for SSRS and looked in the log files - can't find anything useful in the logs/events even after adding http:4 for http logging into ReportingServicesService.exe.config. There's nothing untoward in the trace log file either.
The error message is the generic :
An error has occurred
Something went wrong. Please try again later
We have SSRS running on it's own server. We're accessing the reporting portal on local machines over what appears to be HTTPS but there is no SSL cert on the server. Not sure if this could be the issue but I don't think it would explain why this error has occurred in the the past week.
We're using Edge to access the portal locally.
We're working with our server team to get SSL configured. Are there any other steps I can take to debug this issue?
October 19, 2017 at 11:00 am
Typically this error is from configuration issues. I've always seen it with second message as well as additional information in the Report Server Services log. From what you are saying, you are getting neither of those so that is very unusual. The second message and the reporting services logs would be the other steps.
It could be whatever has been done or changed for SSL. If you don't have a certificate on the SSRS server, you can't setup SSL on the report server. If IIS is on the same computer, that can also have an effect on how SSL connections are processed.
I would double check the changes you made to the configuration file as well as the settings in Reporting Services Configuration Manager.
I'm not sure which log file you checked either - if you made changes to log HTTP errors, those errors are logged to a different log file from the Report server services log (ReportServerServiceLog_<timestamp>.log)
The file name for the HTTP errors log is in the ReportingServicesService.exe.config file
There are two different log files if you enabled HTTP logging and they both have different information. If nothing else, set the Report Server Services trace log to verbose.
Sue
October 20, 2017 at 2:28 am
Thanks - I had to wait for a bit for the http error log to appear.
Microsoft.ReportingServices.Portal.WebHost!reportserverwebapp!d6!10/20/2017-09:07:24:: e ERROR: [mgggtq10]: OData exception occurred: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it {SSRS IP}:443
Looks to be a HTTP SSL issue or firewall ACL issue. This is enough for me to work with my networking/server friends. Thanks for replying.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply