Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

cannot login to reporting services using windows authentication

Posted on 2009-12-18
19
Medium Priority
?
1,167 Views
Last Modified: 2012-05-08
Since rebuilding my PC I am not able to login to MS reporting server using windows authentication, but manually entering domain user and password works OK.

SQL and visual Studio 2005, Windows XP3. Reporting Services sits on Server 2003.

Using SQL server management studio, I was able to login to reporting server using windows authentication, but  now that I have rebuilt the PC, it gives 'unable to login'. However, if I chose basic autherntication, my domain user/pw works fine. I can log into the database server using windows auth without problem. If I use SQL management on the server directly, it logs in using windws auth (though this is then under the Domain Admin account). Any ideas appreciated.
Thanks.
0
Comment
Question by:jostick
  • 9
  • 4
13 Comments
 
LVL 1

Expert Comment

by:N1njaB0b
ID: 26080222
When you rebuilt your PC, did you make sure to re-join the domain?

Just to make sure that you are running SSMS under your domain account, you could try using "runas".
From the command line:
runas /USER:mydomain\myusername "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe"
(of course replacing mydomain and myusername with your domain and username)
0
 

Author Comment

by:jostick
ID: 26191093
Yes, rejoined the domain.
'Run As' suggestion did not work.
Thanks.
0
 
LVL 1

Expert Comment

by:N1njaB0b
ID: 26192353
You mentioned that it works if you are logged on directly to the SQL server as domain admin.  Have you tried logging on directly to the SQL server as yourself?  This would help to rule out the possibility of a rights issue.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 

Author Comment

by:jostick
ID: 26202005
I can log on to reporting server whilst logged on to the Windows server as domain admin and 'run as' SQL management as myself.

I cannot log on to report server from the PC that I have recently built, either as myself or 'run as' domain admin.

I CAN log in by choosing 'basic authentication, and unsing my domain login and password.

It seems that that the loggged in user details are not being passed through in Windows authentication, if that makes sense.....
0
 

Author Comment

by:jostick
ID: 26293172
I did a fresh Windows install (XP SP3) as a have anew hard drive. Immediatly after install, there was no problem using windows authentication (also to deploy reports with VS2005). However, it no longer works. Is this due to further windows update perhaps?
0
 

Author Comment

by:jostick
ID: 26312147
A bit more information:

The problem is that MS SQL management and Visual Studio 2005 (for deploying reports) is not always logging into the report server. I have three client PCs that I'm testing this on . The first (been working for years) always logs in when using Windows authentication. The other two (new machines) occaisionally log in but often don't. So, I know that there is no problem at the server end.

I have copied the SQL2005 and VS 'program folders' and reg settings from the working machine to one of the new ones (desparation!). It makes no difference.

All client PCs are at XP SP3 and SQL2005 SP3. I have tried running SQL without the service packs and initally though that it worked, but then failed again.

I can always log in to report server using Basic Authenticaion and manually entering domain username and password. Its like SSMS is not actually using, or passing, the log in credentials of the current user and I have to force it to use it.

The IIS logs show '401.2' erros when I try to connect.
Sucessfull connections always show a 401.1, but then a 200 withe the domain user login. Its like it tries to log in anonymously first then tries a user name.
2010-01-13 23:58:43 W3SVC2090376784 192.168.xxx.xxx POST /reportserver/ReportService2005.asmx - 8080 - 192.168.xxx.yyy - 401 2 2148074254
2010-01-13 23:58:45 W3SVC2090376784 192.168.xxx.xxx POST /reportserver/ReportService2005.asmx - 8080 domain\user 192.168.xxx.yyy - 200 0 0

Unsucessful attempts do not have the domain\user login entry. Its like there is no attempt being made to login using the domain user account. I think this is the key.

But, what s odd is that it occaisioanlly works OK...

Any help on this is appreciated as its getting really frustrating! Thanks.

0
 

Author Comment

by:jostick
ID: 26312155
Sorry, typo (401.1 instead of 401.2):

Should read: Sucessfull connections always show a 401.2, but then a 200 with the domain user login. Its like it tries to log in anonymously first then tries a user name.
0
 
LVL 1

Expert Comment

by:N1njaB0b
ID: 26323879
I know this seems like a stretch, but this is a pretty wierd problem.  Have you tried adding the report server address to your Trusted Sites list in IE?  Perhaps the credentials aren't being passed (sometimes) because it does not recognize that it is on the Intranet.
It also might be worthwhile to see if your local anti-vrus/firewall software might be inadvertantly stripping credentials out of your outgoing web traffic.
0
 

Author Comment

by:jostick
ID: 26327827
Interesting suggestion, but no joy I'm afraid.

Wierd that it is an intermittent problem as well. Possibly some kind of timeout duirng NTLM exchange?Should have mentioned that clients are linked to server by VPN (but this has worked for the past few years without problem).  If so, it must be something that is configured onthe client as one of the three is 100% reliable.

Worth noting that each Client PC shares same AD configuration

Thanks for the effort!
0
 

Author Comment

by:jostick
ID: 26405559
More info:

I have established that it is not a network problem. This is becasue request s from a browser to report server get logged as 'normal' in IIS (i.e. 401 2 folowed by 200 0). ut, requests from SSMS and VS2005 get 401 2 only  - its like they never try to log in with the user credentials.

Its somehting in the SSMS or VS config....
0
 

Accepted Solution

by:
jostick earned 0 total points
ID: 26439148
\Right. Thisd is now solved!

Problem was that AVG 9 (possibly link scanner) was doing something when VS and SSMS were trying to authenticate. Don't know if htey were blocking or just corrupting the exchnge with  the IIS.

This AVG forum link maybe of use: http://forums.avg.com/ca-en/avg-free-forum?sec=thread&act=show&id=28713

NinjaBob, thanks for the time that you spent posting on this.
0
 

Author Comment

by:jostick
ID: 27595054
Solved problem myself. Can be closed.
0
 
LVL 1

Expert Comment

by:N1njaB0b
ID: 27598634
I respectfully request that my comment (ID: 26323879) be awarded the solution points, since I did suggest checking the local firewall software.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The article covers five tools all IT professionals should know about, as they up productivity by a great deal!
This article is about my experience upgrading my consulting machine to Windows 10 Version 1709 (The Fall 2017 Creator Update)
Viewers will learn how to use the SELECT statement in SQL to return specific rows and columns, with various degrees of sorting and limits in place.
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…

581 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question