January 23, 2019 at 3:06 am
We are trying to implement an AWS load balancer against two Standard Edition instances of SSRS. (This is not a scale-out deployment.) By suitably editing the config file (adding <hostname>ourdomain.com</hostname>) we seem to have got it working against the web service URL but not the portal, ie https://ourdomain.com/reportserver works but https://ourdomain.com/reports doesn't. The latter returns a variety of errors screens. Bypassing the load balancer all works fine on both instances.
The essential point is that ourdomain.com/reportserver works, ourdomain.com/reports doesn't. I am looking for any insight that might help with this specific problem. With respect, I don't really want to get into 'bigger picture' conversations.
October 2, 2019 at 2:00 am
Did you find a resolution to this issue? I'm facing the same issue.
October 15, 2019 at 4:43 pm
We never got load balancing stable with this architecture. We're actually still actually using the load balancer but with only one SSRS instance in it. We could switch to the other instance by placing it into the load balancer instead. It was the HA we really wanted rather than load balancing per se. As things currently stand therefore we have a fairly easy standby SSRS instance but not proper HA.
On a slightly different tack we found that the merge replication on the ReportServer database wasn't stable for deploying and updating reports on both nodes. There were too many conflicts, so we only deploy on the publisher. Then it works quite well.
March 31, 2021 at 11:31 am
This was removed by the editor as SPAM
April 14, 2023 at 8:07 am
This was removed by the editor as SPAM
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply