i am getting "Login failed for user 'NT AUTHORITY\IUSR'" error when web service is access to SQL Server.
Steps i followed :
1) Published web service in IIS (In my system OS is Windows Vista - IIS 7.0).
2) Updated Connection string to local database (I am using SQL Server 2005 install locally).
3) Accessing the web service from applciation.
i am getting "Login failed for user 'NT AUTHORITY\IUSR'" error while hitting database.
Can anyone help me ASAP.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
in the IIS manager, drill down to the web site, right-click it & choose properties.
Choose the Directory Security tab & click Edit under Anonymous access & authentication control.
Either put in a user name that has rights to the SQL server, or disable anonymous access and chose one or more of the authenticated access methods.
R u sure Daniel your coments would work.... ? I don't think its a solution..If the user removes ananymous access the the site will no longer be public access site..It will start asking login's...it would make things complex...
As per the user Issue...I guess the page that is fetching datas from the DB alone is having probs...and not the site itself...
Hello cses,,
1. Is your site Asp.net based and does it connect to DB using Connection string mentioned in Web.config with IP or does it access DB file in your site (LDF , MDF )
2. Does the SQL connection string mentioned in Web.config have proper credentials ..Did you test and login to the MsSql DB in your server with those login and do they have DBO permission over the DB.
3 What DB version are you using in u r server ( PC) MsSql 2000 or 2005 or higher ?
Business Accounts
Answer for Membership
by: servoadminPosted on 2009-01-13 at 07:22:13ID: 23363565
http://mikeplate.wordpress
"
Mike,
Im going to add this information to your blog as it may help other people. Your site is one of the best in terms of describing whats going on with IIS 7 and Classic ASP.
You wrote: Regarding your comment on my blog post about asp scripts on Vista:
What I talked about there was only related to Microsoft Access databases, and probably have no relevance on a SQL Server connection. Your problem seems to be related to identity and integrated security (or lack thereof). The IIS process have the identity NT AUTHORITY\IUSR but that user does not have any permissions to the SQL Server. What identity IIS is running under can be configured, and that is probably what differs between your Vista machine and XP machine.
Im not sure if this information might help?
http://msdn2.microsoft.com
I kept playing around and I finally figured it out you are completely correct in that SQL Server 2000 had a different set of issues than Access under IIS. What I needed to do was to change the security mode from Windows to Windows & SQL Server (this is the mixed mode). This is available under the Enterprise Manager by right clicking on the server name under the SQL Server Group. The top half of the security tab will let an administrator change the authentication mode. I was then able to access the server with ASP by using the following connection string: conn.ConnectionString= Pro
I also tried creating other user names within the security settings of SQL Server and granted them the necessary permissions to the database and each was able to access it.
So in summary, I didnt need to change any permissions on the Temp directory nor did I need to change anything on the Application Pool in order to get Classic ASP to talk to SQL Server 2000 under IIS 7 and Vista. I just wanted to add this out here so that other people who are going through the same headache might have an easier time!
Thanks again Mike for all of the help and suggestions! It is really appreciated!!!!
"
Just for your information from one of the forums...