I have reporting services 2016 and change url protocol from http to https, but if upload the rdl file I have error notification "Something went wrong. Please try again later." and cannot create a new data source with the same error message.
Anyone can help?
Thanks.
August 23, 2023 at 4:09 pm
First step - check the logs. The Windows logs, the SQL logs, and most importantly the SSRS logs.
With what you said, there is nothing for us to go on. The SSRS logs will definitely tell you what went wrong and from there either you or someone on this forum will be able to help.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
August 24, 2023 at 12:27 am
Dear Brian,
I've checked the logs, but can't get any information related to the error. What makes it weird is that I can upload files other than RDL files and can download report files from the reporting service manager.
August 24, 2023 at 1:30 pm
Are you able to (safely) disable any firewall on the SSRS server and try again?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
August 24, 2023 at 2:36 pm
As a quick check before disabling the firewall, what about if you log into the SSRS server and try uploading from the server itself? That SHOULD bypass the firewall.
Since you are using https for this now, is your certificate valid? What I mean is do you get any errors or warnings or any "Not secure" notices in the browser bar?
I also find it a bit odd that the SSRS logs don't contain any information about the issue... They should at the very least be telling you if it is a 5xx error or a 4xx error? What about if you load up the developer console in your browser and then try the upload. That too should tell you if it is a 5xx error or a 4xx error or something else.
Another thought - what about an incognito browser window? I am wondering if it could be an extension issue OR a cache issue. Also, do you have a password manager set up on your browser and if so, is it configured for your SSRS site? I know we've run into issues with password managers that are set to auto-fill and have had to get end users to disable them.
My very last thought is how large is the file you are uploading? I am wondering if you have a limit on the file size to be uploaded to the server.
I am thinking it is not firewall related only because you said other files upload no problem, but it also doesn't hurt to try disabling the firewall like Phil suggested temporarily to see if it helps.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
August 24, 2023 at 2:46 pm
I am thinking it is not firewall related only because you said other files upload no problem, ...
Solid logic.
I had not realised until now that it was possible to upload any old file via the SSRS portal & had assumed that the poster was doing the upload of 'other files' in a different way from uploading RDLs. My previous suggestion is therefore very unlikely to be the issue.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
August 24, 2023 at 3:24 pm
That could be the case Phil, but it also doesn't hurt to try it. I've seen weirder things! I wouldn't rule out the firewall until I have disabled it. The other fun thing is it COULD be the hardware firewall blocking something.
It could even be something crazy like a web filter appliance filtering out RDL file uploads or a browser extension or an antivirus/antimalware tool. The first step (for me) is always to review the logs and if they aren't helpful, then load up a debugger (developer tools). That applies to all applications I work with. C# - is there anything interesting in the windows logs or the application logs? if not, lets load up the debugger and see what's actually happening. SQL Server - is there anything in the logs? if not, lets load up extended events/profiler. SSRS - check the all of the logs (SQL, Windows, and SSRS). If they aren't helpful, lets look at the developer tools. Doesn't mean I'll solve the problem, but I should at least have a good idea of the problem. Web based things if it is 5xx error, then it is server side so I know that I can stop troubleshooting locally and start troubleshooting on the server. If it is a 4xx error, then it is client side, so lets troubleshoot client side. 200 means success so then I just get confused and try having more coffee. And any other numbers mean I am jumping off to google to see what's up.
I mean, I'm having a fun one with a 3rd party I am working with where if I send them an email with a txt attachment and in that attachment it contains the text ".com", then their email filter is grabbing the string and replacing it with their web filter scan tool in it. So if I have "google.com" in the text, it gets replaced with "https://webfilter/scan?URI=google.com&hash=afjsidofy789z607eh4rj3l21457680d6f0sad7g07asdfjhlh432h80u7sadhf6a08shd6fa8b34yl" and that is screwing up the file so they can't automatically process it in their system. The solution - I put it into onedrive and sent them a link to the onedrive version of the file. But why would an email filter butcher a text file? It's not like txt files have clickable links...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
August 25, 2023 at 12:23 am
I opened the report manager directly from the reporting service server. And as I mentioned before, only RDL files cannot be uploaded, while other files can be uploaded.
There is no error message like 403 or something else, and there is no "Not Secure" notification in the URL address field, only a notification "Something went wrong. Please try again later".
There are also no restrictions on the size of files that can be uploaded.
Not only did I experience the error above, to make improvements to existing data sources, I experienced the same thing.
I really appreciate your advice
Problem has been solve, by editing rsreportserver.config, adding <ReportServerUrl>https://servername.domain.com:443/ReportServer</ReportServerUrl>
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply