I encountered the same problem recently on a new server which runs on Windows Server 2016 and MSSQL 2017.
It seems like MSSQL Auditor still does not support MSSQL 2017, which is surprising, given how long it is around
I encountered the same problem recently on a new server which runs on Windows Server 2016 and MSSQL 2017.
It seems like MSSQL Auditor still does not support MSSQL 2017, which is surprising, given how long it is around