Sql connection error

Question

1.00/5 (1 vote)

See more:

SQL-Server-2014

I installed SQL server express 2014 in one system. I am able to connect that system's sqlserver with my system using with sql server management studio. But same thing I tried from visual C# programatically, I am getting error loging failed user sa. in that system i already enabled sa user login. sqlserver authentication.
So why i am unable to connect that from visual c#.

What I have tried:

I googled but, came with no suitable solution

Posted 5-Oct-17 21:14pm

vijay_bale

Updated 5-Oct-17 21:36pm

Add a Solution

3 solutions

Solution 1

Get assistance about connection string using this link
SQL Server connection strings - ConnectionStrings.com[^]

Posted 5-Oct-17 21:31pm

Carlos2017

Solution 2

Have you tried the below guide?? see if these can help you..

[^]

[^]

Posted 5-Oct-17 21:35pm

Atlapure Ambrish

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 · Accepted Answer · 2017-10-05T21:36:00

Solution 3

Without your code, we can't do anything much.
Except to say "never use the sa login" - create users with the right permissions to do their job and no more, and use those instead.

Then look here: Simple SQL Connection String Creation[^]

Posted 5-Oct-17 21:36pm

OriginalGriff

Comments

vijay_bale 6-Oct-17 3:53am

I added connection string in appconfig file like below
<add name="connectionstr"
connectionString="Data Source=192.168.1.10\SQL2016;Initial Catalog=inventoryDB;Persist Security Info=True;User ID=sa;Password=***********"
providerName="System.Data.SqlClient" />

OriginalGriff 6-Oct-17 4:07am

Don't use the sa user: it is an admin login and can do anything. Create your own users!

And what happens when you try to connect to that IP address (I'd use the computer name, myself - the IP can change as computers are powered up in a different sequence) using the link I gave you?

vijay_bale 6-Oct-17 4:17am

As You told I created one new user and give connection string in config file like below
<add name="connectionstr"
connectionString="Data Source=192.168.1.10\SQL2016;Initial Catalog=inventoryDB;User ID=test;Password=***********"
providerName="System.Data.SqlClient" />

I have to try that udl connection string what you told. First I did like this next I will do that also

vijay_bale 6-Oct-17 4:37am

Now I tried with connectionstring file UDL. I changed ip to system name also. but getting same error
<add name="connectionstr"
connectionString="Persist Security Info=False;User ID=test;Initial Catalog=inventoryDB;Data Source=m3\SQL2016"
providerName="System.Data.SqlClient" />

OriginalGriff 6-Oct-17 4:45am

And how are you using it? What code are you reading it with, and opening the connection?

vijay_bale 6-Oct-17 4:48am

to read that connection i am using in my app forms
SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["connectionstr"].ConnectionString);

I already added asembly reference of comfiguration and in also i added
using system.configuration.

OriginalGriff 6-Oct-17 4:58am

And what does the debugger show as the returned connection string?
What happens in your code after that, and what does the debugger show you?

vijay_bale 6-Oct-17 5:00am

I tried In debugging mode and I am getting belo error
"Keyword not supported: 'provider'."

OriginalGriff 6-Oct-17 5:11am

So ... what do you think the error message is telling you to do? :laugh:

vijay_bale 6-Oct-17 5:31am

I don't know what to do sir.

OriginalGriff 6-Oct-17 5:46am

:sigh:
Start reading and thinking about what you are doing, rather than jumping in and guessing.
This link I originally gave you says this:

Remove the bit at the front of the initstring: "Provider=..." up to and including the first semicolon (SQL Server doesn't support the Provider keyword)

And your error message says this:

"Keyword not supported: 'provider'.

So your string - which you need to look at in the debugger - still contains the provider info, which you do not want.
Use the debugger: look at exactly what string you are getting back. You should see the problem!

vijay_bale 6-Oct-17 6:17am

I removed that provider key, now it is connecting

OriginalGriff 6-Oct-17 6:24am

All you have to do is look, read, and think! :laugh:

vijay_bale 6-Oct-17 6:35am

yes abviously

vijay_bale 6-Oct-17 4:49am

Is that ok sir? Is anything I have to change or add?