IIS hosted website cannot access database

Question

0.00/5 (No votes)

See more:

Hi there,

I have a MVC3 application which uses a local database. I have a connection string in web.config file which specifies the connection.

<add name="RoomDB" 
       connectionString="Data Source=.\SQLEXPRESS;Integrated Security=SSPI;Initial Catalog=Room Details;User ID=sa;Password=sa;" 
       providerName="System.Data.SqlClient" />

My application works fine but when I hosted the application in IIS7 in my local system using default app pool, the application can't open the database accessing pages showing the below error.
"Cannot open database "Room Details" requested by the login. The login failed.
Login failed for user 'IIS APPPOOL\DefaultAppPool'."

I think something wrong with connection string or in Application pool.
Please provide me help in this regard.

Thanks in advance,
Naresh S.

Posted 10-Feb-12 17:36pm

S.M.Naresh

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ganesan Senthilvel · Accepted Answer · 2012-02-11T22:30:00

The recommended Microsoft solution is to create a separate account. However, if your solution is small, you can instead add the 'IIS APPPOOL\DefaultAppPool' user as a database user in your SQL instance, then providing the proper 'User Mappings' to the databases you need the DefaultAppPool user to access.

You may not necessarily be able to search for this user, but you can still enter it in the 'Login name' field in the "Login - New" window as "IIS APPPOOL\DefaultAppPool" (without the quotes).

MSDN Reference at: http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/73eee0b4-9eee-4a71-a448-3e3eef9ee404/[^]