Hi, I am continuing a struggle with setting up a scale-out cluster - thought I had it all set up last week. Now I come in this week and it's not working with a 401. Background: SSRS 2008 Windows 2008 R2 Passthrough SSL from F5. Certificates are installed. Additional config performed in the config files and registry to fix issues, which is shown in 2012 instructions, but not 2008. Like I said, all was working fine for a week or so and then - the 401. This has happened twice now and I rebuilt it last time. I disable one node from F5 - so that requests are only being routed to one server and things work. Then I switch so that requests are sent to the other node and everything is still working. Enable both nodes and this message: The request failed with HTTP status 401: Unauthorized. Has anyone seen this? Can you suggest troubleshooting steps? Thanks so much! Sam

Hi Sam, Sorry for the delay. Generally, the HTTP 401 error occurs when the user is not authorized to the Report Server. Besides, if Reporting Services is configured to use Kerberos, however, we didn't register Service Principal Name (SPN) for the account the Reporting Services is running under, this error will occur as well. To solve the issue, please follow these steps: Make sure the user is able to connect to the Report Server (From your descriptions, it seems the service account is fine.). If using Kerberos authentication, please make sure SPN is configured correctly. For more information about Kerbero Authentication and how to register SPN for a report server in Reporting Services, please see: How to: Configure Windows Authentication in Reporting ServicesRegister a Service Principal Name (SPN) for a Report Server If you have any more questions, please feel free to ask. Regards, Mike Yin TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Mike Yin TechNet Community Support

Hi Sam, Sorry for the delay. Generally, the HTTP 401 error occurs when the user is not authorized to the Report Server. Besides, if Reporting Services is configured to use Kerberos, however, we didn't register Service Principal Name (SPN) for the account the Reporting Services is running under, this error will occur as well. To solve the issue, please follow these steps: Make sure the user is able to connect to the Report Server (From your descriptions, it seems the service account is fine.). If using Kerberos authentication, please make sure SPN is configured correctly. For more information about Kerbero Authentication and how to register SPN for a report server in Reporting Services, please see: How to: Configure Windows Authentication in Reporting ServicesRegister a Service Principal Name (SPN) for a Report Server If you have any more questions, please feel free to ask. Regards, Mike Yin TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Mike Yin TechNet Community Support

Hi Sam, Sorry for the delay. Generally, the HTTP 401 error occurs when the user is not authorized to the Report Server. Besides, if Reporting Services is configured to use Kerberos, however, we didn't register Service Principal Name (SPN) for the account the Reporting Services is running under, this error will occur as well. To solve the issue, please follow these steps: Make sure the user is able to connect to the Report Server (From your descriptions, it seems the service account is fine.). If using Kerberos authentication, please make sure SPN is configured correctly. For more information about Kerbero Authentication and how to register SPN for a report server in Reporting Services, please see: How to: Configure Windows Authentication in Reporting ServicesRegister a Service Principal Name (SPN) for a Report Server If you have any more questions, please feel free to ask. Regards, Mike Yin TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Mike Yin TechNet Community Support

Mike, Thanks for your reply. I am running the services under the Network Service account. I had removed this entry from the rsreportserver.config in the past to ensure kerberos was not being used and ruling the spn configuration out as an issue. RSWindowsNegotiate A little more information - the site started working for a few days last week and has now started with the 401 error again.

Hi Sam, Thanks for your posting. Have you defined a virtual server name for the NLB server cluster? Please note that we must use the virtual server name in the Web Service URL and Report Manager URL. Regards, Mike YinMike Yin TechNet Community Support

If I understand you correctly, the virtual server name is rstest.dev.mydomain.com This was defined on the NLB, a certificate was created and then configured in SSRS. I also added this to the BackConnectionHostNames along with node1.domain.com node1 Thanks again for your assistance.

I was getting the 401 error yesterday and traced it back to the second node. I had the first node disabled on the NLB to aid in troubleshooting. At that point SSRS began properly serving up pages from that node.