Thursday, June 13, 2013

SSRS Windows Integrated Security: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

The Overly Complicated Problem
I spent about 2 days trying to figure this problem out, until we had some professional help step in to help us figure it out. The solution is embarrassing. First an overview of the problem. The error show down below is during a connection test for a datasource in SSRS. All of this is taking place in the SSRS 2008R2  Management Portal.

This error reads:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

It unfortunately can be caused by a plethora of configuration issues. This includes: not having the right permissions - which means not being in the right group or being added to the right security context. Security context such as having permissions to a database in SQL Server or even being given the correct permissions in SSRS for a folder or datasource.

In my case, everyone else had access to this datasource except me - totally mind boggling.

My co-workers searched high and low, we even though maybe it was a server configuration issue.
I even thought it had something to do with the SPN of the server which you can read about here:
Alas it was none of those things... it was something incredibly stupid.

The Potential Stupid Fix to the Very Frustrating and Stupid Problem
I can't say this will fix your problem, but it is a good place to start.

Assuming you are using IE to access SSRS (only seems to work properly in IE); add the SSRS server URL to your trusted sites in IE.

  1. Open IE
  2. Go to your internet options [figure 1]
  3. Select the security tab [figure 2]
  4. Select Trusted sites
  5. Click on the Site button
  6. Enter the URI base of your SSRS server's URI (if not using https, remove the check mark from the box) [figure 3] - an example of this is: http://ssrsServerName.contoso.local or if your network is setup for it you can simply use the server name: http://ssrsServerName
  7. Close out and apply everything (Save changes)
  8. Close IE - all tabs and windows
  9. Open IE - your problem should be fixed
Figure 1 - Internet Options

Figure 2 - Trusted Sites

Figure 3 - Add Server URI

This was much harder than it should have been. If this fix didn't work for you it is very possible you need to look into SPN setup and your permissions. I don't have a lot of experience in fixing SSRS, I just deal with the one off issues it spawns on occasion.

If you are using the Development Edition of SSRS I believe (I am not totally sure) that if you are looking for the configuration files that are spoken about here you may not find them. I don't understand why, but I am just giving you a heads up.