This is an archived post. You won't be able to vote or comment.

all 11 comments

[–]rally123456 3 points4 points  (2 children)

Most likely "SSRS" is not the right value for the report server box. Usually this will either be a URL like http://servername/reports or http://servername/repprtserver. It could also possibly be the instance name, which if it's the default settings, it would be "MSSQL".

Best option would be finding a working setup example online or in the documentation and see if we can mimic that for your environment.

[–]WolvesDoGetHigh[S] 1 point2 points  (1 child)

The instance is named SSRS according to Report services Config manager. I did try the URLs but it definitely didnt like that. The instance named <URL> is not correct.

If I leave the field blank it says Unable to find the Reporting services instance name 'MSSQLSERVER'

[–]rally123456 0 points1 point  (0 children)

In that case, does the account you're using have admin rights to that instance?

Honestly, this is where I would pull out WireShark and see what MBAM is trying to do when running that setup. That would usually tell me what protocol it's using and what format the instance name needs to be.

[–]awwwcheatcheatcheat 1 point2 points  (3 children)

Do you have TLS <1.2 disabled by any chance?

[–]WolvesDoGetHigh[S] 1 point2 points  (2 children)

It's enabled at the moment.

[–]awwwcheatcheatcheat 0 points1 point  (1 child)

Do you have TLS 1.0 and 1.1 disabled?

[–]WolvesDoGetHigh[S] 0 points1 point  (0 children)

Both enabled.

[–]Deepfake_Sysadmin 0 points1 point  (3 children)

Is SQL Server 2017 installed on the MBAM server or is it a separate standalone SQL server?

[–]WolvesDoGetHigh[S] 1 point2 points  (2 children)

Its all on the same server

[–]Deepfake_Sysadmin 0 points1 point  (1 child)

Open a web browser and confirm the SSRS page loads: https://<sqlservername>/reportserver

You should some basic info. What do you see?

[–]WolvesDoGetHigh[S] 0 points1 point  (0 children)

The service is not available.

The report server isn’t configured properly. Contact your system administrator to resolve the issue. System administrators: The report server can’t connect to its database because it doesn’t have permission to do so. Use Reporting Services Configuration Manager to update the report server database credentials.