I have a user who can bring up a report in Internet Explorer, but cannot export it to Excel. he gets the following any idea why it would happen? You are not authorized to view this page You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept. -------------------------------------------------------------------------------- Please try the following: Contact the Web site administrator if you believe you should be able to view this directory or page. Click the Refresh button to try again with different credentials. HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration. Internet Information Services (IIS) -------------------------------------------------------------------------------- Technical Information (for support personnel) Go to Microsoft Product Support Services and perform a title search for the words HTTP and 401. Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled About Security, Authentication, and About Custom Error Messages.

Hi, Please could you post more details. Are you running SQL 2005 or SQL 2008. usually these kind of errors occur because of memory limitation. Exporting to excel will consume lot of memory than exporting to CSV. In SQL 2005 the problem is existing. However MS has resolved it in SQL 2K8. You could do a test by running the report for few less data and then exportring it to excel. HTH, Ram

it's SQL 2005 SP2 with a CU and SSRS is in a scale out configuration. Multiple people access this report and can export to excel with no issues. just one person seems to be having a problem. not even sure where to start looking

Hi, One thing is you can compare the IE settings of this user with the other users. Prabably this might help you out in finding the issue. While exporting to excel make sure enough memory is available. HTH, Ram

Hello Alen, The 401.2 error can happen if you don’t have any authentication methods specified in IIS on the specified site or you are attempting to use NTLM through a proxy server. If these two options don’t apply to your scenario, consider following the instructions contained in this msdn blog. http://blogs.msdn.com/b/chaun/archive/2008/02/20/401-2-troubleshooting-for-intranet-websites-using-integrated-authentication.aspx Thanks, Cathy Miller Microsoft Online Community Support

our helpdesk took a look and turned out to be one of the browser toolbars or something similar