Blog
Welcome to the Trioro Tech Blog.
On this blog we post some of the technical challenges and solutions that we've come across. From time to time we also post comments on new technology that we've come across.

Tuesday, September 23, 2008

SQL Reporting Services - 401 Error & rsLogonFailed

We've been using SQL Reporting for awhile now.
Accessing the reports was done by going to http://localhost/ReportServer/

I recently wanted to delete an existing report and to do that needed to access the report server management at http://localhost/Reports/
At this point I was getting a 401 error and could not access the control panel.

This was resolved by adding a registry key to disable a loopback security check that had been implement by a Windows Server Service Pack.
Step by step instructions to fix this issue are available here:
http://aspadvice.com/blogs/ssmith/archive/2007/02/09/SQL-Reporting-Services-401-Error.aspx

One of my earlier troubleshooting steps had been to use Reporting Configuration Manager to update the Unattended Execution Account.
I entered a user with a high level access.  That didn't do anything to fix by 401 issue (eventually solved using the instructions above).  But I never went back to remove the service execution account.

Going back to run the reports that had previously been running fine, I was now getting this error...

Logon failed. (rsLogonFailed) Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)

Other solutions offered that the username / account I was using to run the reports was wrong.  However, these reports had been working fine prior to me fiddling that unattended execution account.

I got my rsLogonFailed issue resolved by completely disabling the Execution Account.  This was fine for the reports that we need to run.

Blogged with the Flock Browser

Labels: ,

0 Comments:

Post a Comment

Links to this post:

Create a Link

<< Home