Forum Discussion
Save Report to Secure (HTTPS) Server
That approach is something that I tried initially but every time, even the most simple report returns:
An error has occurred.
There was an error uploading your .pbix file. Verify that the file has not been corrupted and that the file extension matches the format of the file.
In looking at the log files for this error I see:
|ERROR|20|The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.| RequestID =
|INFO|55|Sending response. Response code DOMAIN\EAWR 422, Elapsed time 0:00:00.0265593| RequestID =
My client is a government agency and all of their services are required to be secure (HTTPS) which is a pretty fundamental capability of a modern system.
I am kind of surprised that I am having this level of difficulty with getting it to work, asking the security folks to open port 80 is just not an option.
Super User
EAWright wrote:
Could not establish trust relationship for the SSL/TLS secure channel.
That could indicate an issue with your certificate. I'm not really an expert on certificates, but if there is a problem with the trust relationship to the certificate authority it could cause an issue like this. Maybe go back and talk to whoever generated and installed the certificate.
I've setup a couple of Report Server instances with HTTPS and it was just a matter of getting our domain admins to create and install a certificate and then I picked the installed certficate from the Report Server Configuration Manager and it all worked. So Report Server definitely supports HTTPS and it's normally pretty easy to setup.
So I worked with with a second set of eyes to test the out the Certificate, and in continuing to poke around we discovered that we can upload pretty much any file except a .pbix. (.txt, .pdf etc)
We even tried uploading a .txt file with the extension changed to .pbx and received the same could not establish trust relationship error.
Could there be a configuration that I missed when setting up the server/ service ?
I should also mention that I confirmed that the version of the desktop software matches the server version number
- d_gosbell
So that kind of makes sense as PBIRS is written as a number of components. There is a RSPortal service (which renders the User Interface), a ReportingServicesService (which handles the paginated reports) and an RSPowerBI (service which handles the pbix files) and there is a hosting and management component also.
So what this sounds like is some sort of break down around the RSPowerBI component. Unfortunately this is not something I've ever seen before. You might need to consider raising a support ticket with Microsoft for this as I think it's going to need a deeper level of investigation. I have 4 different PBIRS installs in our organization, 2 dev enviroments using http, but both our Test and Prod are NLB clusters using HTTPS. We had a few issues with the test/prod clusters, but that was related to load balancing issues (we accidentally skipped one of the configuration steps), but the https configuration worked fine.
So, in my continued exploration of my issue, I learned that .PBIX is essentially a zip file. With my experience in being able to upload anything but a .PBIX named file I also tried a .zip file and that was blocked as well. (as did many other made up file extensions)
I am curious to know if perhaps there is some filter somewhere that is only allowing known file types and .PBIX is falling over because said filter is seeing them as either a) a .zip file in disguise or b) it does not know what it is and therefore is blocking it.