August 30, 2019 at 3:58 pm
Found the problem:) there was a change log of somebody being stupid and changing the service account for the data source which broke it and they decided not to say anything to anyone
August 30, 2019 at 3:58 pm
Note: Sorry, my grammar is not the best, horrible about run-on sentences. 😉
August 30, 2019 at 5:20 pm
Do you have clustering/load balancing in your environment? We had an issue with report subscriptions sometimes failing, and it turned out that we had two servers in the cluster that weren't synched up, so only one of them knew about some of the the subscriptions. If the good one was live, everything was fine, but if it switched over to the other server some subscriptions stopped working. Getting both servers upgraded to the same settings fixed the issue. Your issue is likely something different, but I thought I'd toss that out just in case it leads you somewhere useful.
August 30, 2019 at 5:23 pm
I appreciate the response but no this is not the case here.. we arent using any sort of clusting or fail over AGs with this.
It is a SSRS 2016 on SQL Server 2016 though.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply