Touble connecting to a SQL server.

Question

0.00/5 (No votes)

See more:

I have two lines of very basic code written in visual studio vb.net to connect to a SQL server that works fine in one instance of visual studio, but does not work when copied over to another instance. I have checked that all the necessary references are included in both instances. Further complicating the issue is that I can connect to a different SQL server in both instances, but I can connect to the server I want in only one instance. Does anyone have a thought as to what may be different between the instances of Visual Studio that would cause this behavior?

The error I am getting is that the server cannot be found. The connection string is identical in all cases

 Dim con As New SqlConnection("Data Source=server1;Initial Catalog=somedatabase;User ID=myid;Password=mypassword;Encrypt=False;TrustServerCertificate=False")
con.Open()

I appreciate any ideas. This is throwing me for a loop.

What I have tried:

I have tried copying the same code to other existing programs and it works just fine. When copied to a new program, it fails.

Posted 26-Apr-17 4:57am

Member 13154057

Updated 26-Apr-17 10:02am

Add a Solution

Comments

ZurdoDev 26-Apr-17 11:32am

You should put the exact error, but if it is that the server cannot be found, that is the error. Perhaps a firewall is blocking, perhaps that server has a sql instance and not a default. Perhaps you need to use IP of server. There's no way for us to know.

2 solutions

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 · 2017-04-26T06:11:00

This is a perfect example of why you don't hardcode connection strings!
You need to provide a connection string with a full reference to teh instenace of SQL server, which normally will be something like "COMPUTERNAME\SQLINSTANCE NAME".
For example, one of mine is:

DataSource=GRIFF-DESKTOP\SQLExpress;Initial Catalog=...

You can only normally get away with just the instance name on local DB's

You also need to check that the SQL Server instance is configured to allow remote connections as this is often disabled for security reasons.

Maciej Los · Answer 2 · 2017-04-26T10:02:00

Solution 2

Please, read this: SQL Server connection strings - ConnectionStrings.com[^]

Posted 26-Apr-17 10:02am

Maciej Los