Veeam Reporter SSRS settings

[tvbc]

Hi,

I am trying to point Veeam to a SSRS server which is a different server from where the database resides. For the URL I have enterred

http://myssrsserver/Reports

and then

mydomain\myusername
mypassword

But I keep getting 404 not found, or 401 unauthorized. I have tried using the SA account, and have the same issue. If I browse to that URL, I can successfully access the reports page.

Has anybody else experienced these problems?

Many Thanks,
Tvbc

[Vitaliy S.]

Hello, could you please tell what version of SSRS are you trying to point to? Have you used this SSRS server with Reporter installation before?

[jeremy]

I am having the same issue.....what is the fix please

[jeremy]

Using SQL 2008R2

[Gostev]

Please make sure you follow system requirements. The product requires SQL 2008 (not R2), so this might be a problem.

[Pavel Shterlyaev]

Please try http://myssrsserver/ReportServer instead of http://myssrsserver/Reports

[Libran_Dragon]

Hi,

You need to add your LAN account to either one of the following groups on the SSRS box..

Veeam Reporter Administrators (Members of this group can manage Veeam Reporter data collection jobs and other settings, and generate the reports)

or

Veeam Reporter Viewers (Members of this group can generate the reports)

Hope this helps

[ddan]

I had the issue where ssrs was configured fine and could browse to it via browser, but then from Veeam Reporter when i'd try to connect via 'configuration' > 'settings' > 'SSRS Server' > 'test' I would get: The request failed with HTTP status 401: Unauthorized. This fixed it for me:

On the Reporting Services Server, open the config file rsreportserver.config (you find it in the Reporting Services folder)
Look for the Autentication configuration node
Remove the RSWindowsNegotiate setting
The config section in question should now look like this:

<Authentication>
<AuthenticationTypes>
<!-- <RSWindowsNegotiate/> -->
<RSWindowsNTLM/>
</AuthenticationTypes>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Autentication>

That way, only NTLM is used for authentication. This fixed it for me

[Vitaliy S.]

Hello Diyan,

Thank you for finding time to update this topic with the resolution.