How to stop Internet Explorer prompting for username and password with SSRS

Stopping Internet Explorer prompting for username and password when you connect to SQL Server Reporting Services (when the SSRS server is on the local Intranet (hint, hint)) could be one of those problems that you never end up resolving. No matter what you change, every time you close IE and open it again it prompts you to log in. This can drive you, and possibly more importantly your customers, around the bend.

Click to enbiggen

For information we are running SSRS 2012 with SSL enabled, browsing to a FQDN, eg. https://reportserver01.domain.local/Reports/ using IE 8 or 9.

There are so many web pages that deal with this and any one of them could work for you - it's a matter of trial and error working through the suggestions.

I had this issue today but against all odds I managed to resolve it. Turns out to be pretty simple but it may not work for you. If not there are some links at the bottom of this post that may or may not help.

If the SSRS server is on your local intranet it is a matter of adding it into the Local Intranet zone in IE:

Internet Options à Security à Local Intranetà Sites à Advanced à Add the URL

Click to enbiggen

Hope this helps somebody.

Paul

Links:

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/6793052f-fc96-4c6b-9c04-9119bc33c804/report-manager-2008-r2-prompts-for-usernamepassword-does-not-accept?forum=sqlreportingservices

http://forums.asp.net/t/1437976.aspx

Comments

How to create a custom Windows Event Log view and email trigger

The filtering on Windows event logs can be slow, clunky and although you can do it on fields like event ID, it seems that many event IDs are shared amongst many different errors – the event ID may match but the body of the error (therefore the actual error) may be completely unrelated. Fortunately, it is possible to filter on the contents of the body of the error message but it requires creating a custom XML query. Also, it would be handy to send out a notification email when this event gets logged. Read on to find out how to work this magic…. This example is looking for a Warning event 1309 for ASP.NET 4.0.30319.0 on a web server. If you were to just filter the log on the criteria above today it would return 435 results because it is a fairly general error ID. If I filter it using XML for SqlException (what I’m really interested in) only 5 results are returned. So the first step is go to the Application Log and choose Create Custom View… Select the XML tab, check Edit

How to configure the SSAS service to use a Domain Account

NB Updating SPNs in AD is not for the faint hearted plus I got inconsistent results from different servers. Do so at your own risk! If you need the SSAS account on a SQL Server to use a domain account rather than the local “virtual” account “NT Service\MSSQLServerOLAPService”. You may think you just give the account login permissions to the server, perhaps give it sysadmin SQL permissions too. However, if you try and connect to SSAS remotely you may get this error: Authentication failed. (Microsoft.AnalysisService.AdomdClient) The target principal name is incorrect (Microsoft.AnalysisService.AdomdClient) From Microsoft: “A Service Principle Name (SPN) uniquely identifies a service instance in an Active Directory domain when Kerberos is used to mutually authenticate client and service identities. An SPN is associated with the logon account under which the service instance runs. For client applications connecting to Analysis Services via Kerberos authentication, th

Fun and games with the Management Data Warehouse (MDW and Data Collectors)

The SQL Server Management Data Warehouse (when you first come across it) seems to promise so much if the verbiage from Microsoft and some other websites is to to believed. But when you install it you may find that it is not as useful as it could be. This is a shame but we are currently only on v2 of the product with SQL 2012 so one hopes it will improve in subsequent versions. However, it probably is worth playing with if you have never used it before - at least you can show your boss some reports on general server health when he asks for it and you have nothing else in place. There is one big problem with it though if you decide that you don't want to use it any more, uninstalling it is not supported! Mad, I know. But as usual some very helpful people in the community have worked out, what seems to me, a pretty safe way of doing it. I had a problem with my MDW. The data collector jobs were causing a lot of deadlocking on some production servers and impacting performance. I

SQL Server Snippets | Paul Hewson

Search This Blog