Connecting to SQL server using windows authentication in VB.NET

Question

0.00/5 (No votes)

See more:

Hi sir,

I need to

Connecting to SQL Server using windows authentication in vb.net

i got the error like this

Cannot open database "FTS" requested by the login. The login failed.
Login failed for user 'IIS APPPOOL\DefaultAppPool'.

What I have tried:

<connectionStrings>

<add name="ConnectionString" connectionString="Data Source=.\sentil;Initial Catalog=FTS;Integrated Security=True;Encrypt=False" providerName="System.Data.SqlClient;Max Pool Size=200" />

</connectionStrings>

Posted 5-Jun-24 18:37pm

senthilnathan p

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)

OriginalGriff · Answer 1 · 2024-06-05T18:53:00

Basically, it's a bad idea to use WA in a website - which is where the IIS APPPOOL\DefaultAppPool bit is coming from.
Because IIS runs under a "generic user" rather than a specific, logged in, "real-world" user, that is the ID that you are trying to connect to your DB using - and if it worked (and it looks like the DB admin hasn't enabled it) then that user would have to have significant DB privileges, which is a very poor idea in a web-based setting. Think about it: if you set up a DB user and log in as them, you can give that user just the permissions he requires to do the job: Read only perhaps, or maybe add Update and / or Insert - but no row delete, or no table delete. That means that any hacks that try to damage your DB can be mitigated because the only user they can access doesn't have permissions to do that!

Use a proper SQL User and things get safer, and easier to manage.