B
Brian-W
I'm trying to setup MBAM 2.5SP1 on Server 2016 using a SQL 2016 on a Failover Cluster (but not using AO).
The initial database configuration went smooth, but setting up the next step (Reports) is causing an issue because it cannot find the instance of the report server.
"Unable to find an instance of the Reporting Services.
That said, I realize that the report server is not supported with the failover cluster, but is there a way to point the Report feature to another SQL server or a server that has the reporting services (ie: one of the Failover cluster nodes) instead of auto-detecting the SQL failover cluster name/IP?
I'm trying to avoid having a SQL server just for MBAM if I can avoid it (for cost and manageability reasons).
Continue reading...
The initial database configuration went smooth, but setting up the next step (Reports) is causing an issue because it cannot find the instance of the report server.
"Unable to find an instance of the Reporting Services.
That said, I realize that the report server is not supported with the failover cluster, but is there a way to point the Report feature to another SQL server or a server that has the reporting services (ie: one of the Failover cluster nodes) instead of auto-detecting the SQL failover cluster name/IP?
I'm trying to avoid having a SQL server just for MBAM if I can avoid it (for cost and manageability reasons).
Continue reading...