Forum Discussion
Save Report to Secure (HTTPS) Server
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
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.
EAWright wrote:
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.
There is a whitelist of known file types that PBIRS will allow (you can edit this list by connecting to PBIRS using Management Studio), but pbix is one of the allowed file types. zip files and other random file types being blocked is the expected behaviour.
As I mentioned earlier, pbix files are handled by a dedicated service, so they are treated differently from any other file type. I still suspect that something strange has happened in your environment and the best way to fix this would be to engage a Microsoft support engineer by raising a support ticket.
Okay new development, when I remove the certificate / 443 configuration uploading a file on the host server works. However with adding the cert back in, even using the port 80 url causes the error to come up agian.