HELP! 401 Authentication - Nothing Is Working!
Hi all, I've recently installed a fresh copy of SSRS 2008 for the first time (SQL SERVER 2008 EXPRESS SP2). Straight install. No changes. And of course, it doesn't work! I was able to get to my report manager page, but only after removing RSWindowsNegotiate and RSWindowsNTLM from the rsreportserver.config file and changing it all to RSWindowsBasic. I don't know why that worked, but it did. But now I can't authenticate to my web service. I keep getting 401 errors, and nothing seems to work. I am at my wits end here. Here is what I have tried: FYI, I am using Windows XP SP2, and VS 2008. 1) Changed the rsreportserver.config file so that it uses "RSWindowsBasic". 2) I have opened the Computer Management tool, and in the 6 SQL Server groups, I have added "Administrators", "NT AUTHORITY\SYSTEM", "ASPNET", and "NT AUTHORITY\NETWORK SERVICE". 3) My Execution Account in SSRS Config is "[MACHINE]\LocalSystem". 4) The Report Server Service Account is "Local System". 5) On the "Services" dialog, RS is running as "Local System". 6) My RS code is: rs.Credentials = System.Net.CredentialCache.DefaultCredentials; I assumed this means it runs as ASPNET on my development machine from VS 2008. I have read and re-read everything I can find on this site. I can't think of anything else left to do. I keep reading the same suggestions over and over. What haven't I done? Why isn't it working? Please give me something new to try. I just don't understand what is wrong. I've added EVERYTHING I can think of to the group "SQLServerReportServerUser$DNB01$MSRS10_50.SQLEXPRESS" and all the other SQL Server groups. Is there some other group I can create and add to? Thanks, Michael
October 21st, 2010 2:02am
Hi Michael, Make sure the user account being used was added to the following security policy Access this computer from the network This policy is found in gpedit.msc Computer Configurations-->Windows Settings-->Security Settings-->Local Policies-->User Rights Assignments Adding the user to this policy If the issue persists, look into the detailed error message from the error logs. thanks, Jerry
October 25th, 2010 6:31am