I’d like to preface this by saying I’m not a DB admin nor have any formal training in DB administration, but trying to get an response in a reasonable time from our network team is like pulling teeth. Some of the terminology or usage of words might not be exact, but hopefully I’m getting it right, and while I might not get an exact solution, it might give me some ideas on what to investigate.

So we have an application on running on one server, and it points to an availability group listener name which has 2 servers under it.

Whenever this AG fails over from one server to the other, this seems to break the SSRS connection. Documents from the application which print via SSRS no longer print out. I try stopping/starting the print spooler and the reporting services on both the DB servers, but it doesn’t do anything. Thus far the only thing that seems to work is rebooting the application server, after which everything that should have printed starts printing out immediately. We have other types of documents from the app that don’t use SSRS, and these print out fine. Obviously I don’t want to be doing this every single time it fails over as it means users have to stop what they’re doing to reboot the server.

The SSRS data connection on both DB servers are pointing to the listener name, not specific server names.