Mssql error unable to connect using the connection information provided retry profile creation

Mssql error unable to connect using the connection information provided retry profile creation

The first step is to install the mssql extension

First find the sql server (mssql) extension in the vs code extension, and download and install it.

After downloading, there will be a section of sql server. (Please ignore the already connected database)

The second step is to connect to the connection steps given in the sql server official documentation

Please follow the steps below to create a connection profile and connect to sql server.

Press «ctrl» + «shift» + «p» or «f1» to open the «Command Panel».

Type sql to display the mssql command, or type sqlcon, and then select «ms sql:connect» from the drop-down list.

Can also be connected directly in the extension

The official wording is a bit obscure,If it ’s not easy to understand,You can follow my operation,As shown in the figure, click the + sign on the right side of connection to create a new connection,The connection property configuration box will pop up.

The third step is to configure the connection properties

Fill in the pop-up attribute configuration according to the database to be connected

The server name or ado connection string specifies the sql server instance name

If you connect to a local database here,Just fill in localhost directly, for other references.

Use localhost to connect to the sql server instance on the local computer. If i want to connect to a remote sql server, enter the target sql

The name of the server, or its ip address. To connect to the sql server container, specify the ip address of the container host.

If you need to specify the port,Use a comma to separate it from the name. For example, for a server listening on port 1401,Please enter, 1401.

«Database Name» (optional)

Here you can fill in the database to be used,You can also leave it as the default database. To connect to the default database,Please do not specify the database name here.(I filled it wrong when I started it,Error when connecting later)

I chose the database test here.

Here I started to fill in the wrong database name because of the wrong understanding,Encountered the following error.(mssql:error:unable to connect using the connection information provided. retry profile creation?), I saw on the blog that I had the same problem as I encountered,Send out the error message,Easy to search.This error will not be reported as long as the information at each step is checked correctly.

3. Authentication type

Select «Integrated» or «sql login». Alternatively, you can enter the database’s ado connection string here. Just choose the first sql login here.

If «sql login» is selected, enter the user name that has permission to access the database on the server.

Just fill in the username of the database here,Like mine:sa

Enter the password of the specified user.

6. Save the password

Press «enter» to select «Yes» and save the password. Select «No» and the system will prompt for a password each time the connection profile is used.

7. Configuration file name «(optional)

Type the name of the connection profile,For example, the localhost configuration file.

8. The configuration is completed,At this point, you can operate the sql server in the vs code.

Refer to the official Microsoft document:create and run transact sql script using visual studio code

Источник

Failed to connect #600

Steps to Reproduce:

1. Install .Net Core instructions
2. Create or open a SQL file
3. Connect to SQL Server
4. Create Connection Profile

The text was updated successfully, but these errors were encountered:

@yasinguzel have you verified that SQL Server is active on the serverport you’re connecting to and there are no firewalls blocking the traffic.

The error message says failed to connect to «127.0.0.1:1433». Is this a SQL on Linux instance running in a local Docker instance? Do you have a way to verify connectivity using an alternate tool such as sqlcmd?

I’m closing this as we haven’t received updated information. If you want to reopen please add in the information Karl requested and we can take another look.

I also have this issue when trying to connect localDB from vscode with mssql extension.

[9:51:01 PM] Error connecting to server «sqllocalDBMyTestingDB». Details: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 — Error Locating Server/Instance Specified)

@sainawkham can you connect from other tools or from your app code? Generally localdb server connections should be in the format (localdb)MSSqlLocalDb or (localdb)MyInstance . I verified this works fine for me and would suspect the issue is using sqllocalDB instead of (localdb) . Similarly, is MyTestingDb your database name? If that’s the case, likely you want to use (localdb)MSSqlLocalDb as your server name and MyTestingDb as the database name when creating the profile.

@kevcunnane it was ok when i use pipe name instead of servernameinstancename. But i’d like to know why i can’t connect with name if there is an answer.

@sainawkham can you confirm the exact connection string used? You can see it by choosing the «Manage Connections» command and choosing to Edit them — this brings it up in the settings. So long as it doesn’t contain a password, could you show it here (since it’ll be a localdb instance and therefore not something anyone else could access)?

Also for OS version, which Windows version (10, 8.1, etc.) are you on? Thanks.

@kevcunnane Sorry for my delay reply.
here my connection string

<
«window.zoomLevel»: 0,
«mssql.connections»: [
<
«server»: «np:\.pipeLOCALDB#57B9D9BBtsqlquery»,
«database»: «»,
«authenticationType»: «Integrated»,
«password»: «»
>
]
>

My OS is windows 10.

OK, so that’s your connection after using named pipes. When using the server name, what is listed for the «server» option?

hi
im using ubuntu 20.04 and install vscode and mssql plugin

but error run create db command
mssql: Error: Unable to connect using the connection information provided. Retry profile creation?

Источник

Integrated authentication failing when attempting to connect to SQL Server from macOS Sierra #22863

This issue is originally discussed here.

Following the Kerberos Setup Instructions. Steps 1 through 3 work perfectly. However, when attempting step 4 I get the following:

Per @kevcunnane request, I’m submitting an issue here.

The only other thing I’ve noticed since the other issue, is that if I run the klist command without first running the kinit command I have several other entries:

We do use the Jamf Casper Suite to manage our Macs, and I’m assuming that’s what those other entries are from.

Finally, I also setup a .Net Core Console app to see if integrated security would run from there, following along the same lines as this issue and I received the same exception as the one the VS Code is giving me with the mssql extension.

The text was updated successfully, but these errors were encountered:

For clarity, updated to dotnet 2.0.0 and still seeing the issue.

This has not been assigned any milestone. Can we get an idea on the timeline? Thanks.

• status: An unsupported mechanism was requested
• minorStatus: unknown mech-code 0 for mech unknown

We need to get information from System.Net.Security team under what condition that status / minorStatus message we get.

Do you have the following two lines in your

/.ssh/config file, or in your /etc/ssh_config ? :

The first is required to enable GSSAPI (Kerberos) authentication, the second one is required to get ssh to canonicalize the hostname via DNS and use the canonical name to obtain a host service ticket. Without the second one, ssh will use the exact hostname or IP address entered on the command line to try and obtain a host service ticket, and in this case it fails.

@geleems I created the config file in

/.ssh/config and added these two settings.

I then restarted but realized I should have first gone back through the original setup document. After I did that, it connected! So, looks like that document needs updated with your suggesting of adding these two lines into an ssh config file.

Would that be something that makes sense for everyone to make sure they have setup? Seems confusing to me why it would work for many others but not me?

Thanks so much for your help @geleems!!

@geleems This did not work for me. Note: My mac is domain joined. I login as the domain user to the mac.

/.ssh/config file (was missing):
GSSAPIAuthentication yes
GSSAPITrustDNS yes

Created /etc/krb5.conf file (was missing):
[libdefaults]
default_realm = DOMAIN.COM

[realms]
DOMAIN.COM = <
kdc = adservername.domain.com
>

Ran:
kinit myuser@domain.com
entered my domain password.

klist (note I first tried kinit with lowercase domain.com, then uppercase DOMAIN.COM)

Issued Expires Principal
Sep 25 11:43:16 2017 Sep 25 21:43:16 2017 krbtgt/DOMAIN.COM@DOMAIN.COM
Sep 25 11:43:46 2017 Sep 25 21:43:16 2017 HTTP/SERVERNAME1.DOMAIN.com@DOMAIN.COM
Sep 25 11:46:13 2017 Sep 25 21:43:16 2017 HTTP/SERVERNAME2@DOMAIN.COM
Sep 25 11:59:30 2017 Sep 25 21:43:16 2017 cifs/SERVERNAME3@DOMAIN.COM

In VSCode:
Create Create Connection Profile
sqlservername.domain.com
dbname
Integrated
profile name

Still get the same error.
mssql: Failed to connect: Cannot access Kerberos ticket. Ensure Kerberos has been initialized with ‘kinit’.
mssql: Error: Unable to connect using the connection information provided. Retry profile creation?

Rebooted my computer and tried again in VSCode.
Still get the same error.

Источник

Setup is unable to connect to SQL Server with connection information.

The only thing I can think of is the names. Because I deleted a previous SCCM Install because we had missed pre-reqs before installing. I went back extended AD and went through all pre-reqs very carefully. I have confirmed that the firewall is disabled, it is not configured to use dynamic ports, firewall is disabled, and I am pretty sure the account used to run setup has permissions to connect to the specified SQL server instance. I am completely stuck here.

Popular Topics in Microsoft SQL Server

Brand Representative for Microsoft

Open SQL Server Configuration Monitor and make sure TCP and named pipes are enabled on the instance. Is SCCM on the same server as the SQL instance or a remote server?

Step 3 of this how-to I wrote shows you a screen shot where you can see if TCP and named pipes are enabled or not:

Brand Representative for Microsoft

Can you connect to the SQL Server instance using the credentials being used to run setup?

Yes, I am looking at MS SQL Server Management Studio and I can see I am connected.

Brand Representative for Microsoft

Is it a default instance or a named instance of SQL Server? How is the server info entered in SCCM?

I am new at SQL, little confused by instances and server names not sure how sql refers to them. When I go to launch SQL Server Management studio, local appears under server name, ive also tried the actual servername, Windows Authentication is being used. I hit connect and it brings me to a local db.

Brand Representative for Microsoft

Open SQL Server Configuration Monitor and make sure TCP and named pipes are enabled on the instance. Is SCCM on the same server as the SQL instance or a remote server?

Step 3 of this how-to I wrote shows you a screen shot where you can see if TCP and named pipes are enabled or not:

Ok named pipes were not enabled. Let me try reinstalling now.

SCCM and SQL are on the same server.

No that didn’t work. Same error.

Brand Representative for Microsoft

How have you entered the SQL connection info in the SCCM setup?

I will PM you this. Thanks.

Just want to give credit for taking the time to review my PM and helping solve my issue.

SCCM doesn’t always like the Default Named Instance’s so therefore by creating a new named instance and providing that instance name to the SCCM Setup Wizard should fix the issue. I am testing this now to confirm it resolved the issue.

Big Thanks to Robert.

I have the same problem. I did all the configurations (TCP 1433, pipes,etc. ) and I can’t continue the setup.

SQL in local server

With the user I launch the wizard I can connect whitout problem to SQL management studio.

Anyone can help me (3 days with this. ( )

Brand Representative for Microsoft

As a matter of etiquette, please start a new post for your issue, don’t piggy back on someone else’s post.

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

poor wifi, school’s third floor

I work as a help desk technician at a high school for a school district. Teachers/students on the building’s third floor have been reporting poor wifi, with their Chromebooks/laptops etc experiencing slow connectivity and random disconnections. We hav.

Need help crafting a job posting for an IT Pro

I’d really appreciate some thoughts and advice. I’m looking to hire an IT pro to be our resident go-to for all things IT (device support, SQL Server, network admin, etc) but who also is interested in learning — or even has some experience in — the.

Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: January 13, 1874: Adding Machine Patented (Read more HERE.) Bonus Flashback: January 13, 1990: Astronauts awakened to the song Attack of the Killer Tomatoes (Read mor.

Spark! Pro series – 13th January 2023

Happy Friday the 13th! This day has a reputation for being unlucky, but I hope that you’ll be able to turn that around and have a great day full of good luck and good fortune. Whether you’re superstitious or not, .

Источник

The first step is to install the mssql extension

First find the sql server (mssql) extension in the vs code extension, and download and install it.

After downloading, there will be a section of sql server. (Please ignore the already connected database)

The second step is to connect to the connection steps given in the sql server official documentation

Please follow the steps below to create a connection profile and connect to sql server.

Press «ctrl» + «shift» + «p» or «f1» to open the «Command Panel».

Type sql to display the mssql command, or type sqlcon, and then select «ms sql:connect» from the drop-down list.

Can also be connected directly in the extension

The official wording is a bit obscure,If it ’s not easy to understand,You can follow my operation,As shown in the figure, click the + sign on the right side of connection to create a new connection,The connection property configuration box will pop up.

The third step is to configure the connection properties

Fill in the pop-up attribute configuration according to the database to be connected

The server name or ado connection string specifies the sql server instance name

If you connect to a local database here,Just fill in localhost directly, for other references.

Use localhost to connect to the sql server instance on the local computer. If i want to connect to a remote sql server, enter the target sql

The name of the server, or its ip address. To connect to the sql server container, specify the ip address of the container host.

If you need to specify the port,Use a comma to separate it from the name. For example, for a server listening on port 1401,Please enter, 1401.

«Database Name» (optional)

Here you can fill in the database to be used,You can also leave it as the default database. To connect to the default database,Please do not specify the database name here.(I filled it wrong when I started it,Error when connecting later)

I chose the database test here.

Here I started to fill in the wrong database name because of the wrong understanding,Encountered the following error.(mssql:error:unable to connect using the connection information provided. retry profile creation?), I saw on the blog that I had the same problem as I encountered,Send out the error message,Easy to search.This error will not be reported as long as the information at each step is checked correctly.

3. Authentication type

Select «Integrated» or «sql login». Alternatively, you can enter the database’s ado connection string here. Just choose the first sql login here.

4. Username

If «sql login» is selected, enter the user name that has permission to access the database on the server.

Just fill in the username of the database here,Like mine:sa

5. Password

Enter the password of the specified user.

6. Save the password

Press «enter» to select «Yes» and save the password. Select «No» and the system will prompt for a password each time the connection profile is used.

7. Configuration file name «(optional)

Type the name of the connection profile,For example, the localhost configuration file.

8. The configuration is completed,At this point, you can operate the sql server in the vs code.

Refer to the official Microsoft document:create and run transact sql script using visual studio code

[1]:

to sum up

• Can you connect to the SQL Server instance using the credentials being used to run setup?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Yes, I am looking at MS SQL Server Management Studio and I can see I am connected.

  Our domainsccmadmin.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Is it a default instance or a named instance of SQL Server? How is the server info entered in SCCM? 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  I am new at SQL, little confused by instances and server names not sure how sql refers to them. When I go to launch SQL Server Management studio, local appears under server name, ive also tried the actual servername, Windows Authentication is being used. I hit connect and it brings me to a local db.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Open SQL Server Configuration Monitor and make sure TCP and named pipes are enabled on the instance. Is SCCM on the same server as the SQL instance or a remote server?

  Step 3 of this how-to I wrote shows you a screen shot where you can see if TCP and named pipes are enabled or not:

  https://community.spiceworks.com/how_to/124598-find-the-port-sql-server-is-using-and-change-a-dynami…

  
  1 found this helpful
  thumb_up
  thumb_down
  

• 

  Ok named pipes were not enabled. Let me try reinstalling now.

  SCCM and SQL are on the same server.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  No that didn’t work. Same error.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• How have you entered the SQL connection info in the SCCM setup?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  I will PM you this. Thanks!!!

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Just want to give credit for taking the time to review my PM and helping solve my issue.

  Recap:

  SCCM doesn’t always like the Default Named Instance’s so therefore by creating a new named instance and providing that instance name to the SCCM Setup Wizard should fix the issue. I am testing this now to confirm it resolved the issue.

  Big Thanks to Robert!!!

  
  1 found this helpful
  thumb_up
  thumb_down
  

• 

  I have the same problem. I did all the configurations (TCP 1433, pipes,etc…) and I can’t continue the setup…

  SQL in local server

  With the user I launch the wizard I can connect whitout problem to SQL management studio.

  Anyone can help me (3 days with this….:( )

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• As a matter of etiquette, please start a new post for your issue, don’t piggy back on someone else’s post.

  
  Was this post helpful?
  thumb_up
  thumb_down