Ошибка субд login failed for user sa

I’ve written a very simple JDBC login test program. And after all kinds of problems I’ve almost got it working. Almost, just can’t seem to get past this problem:

SQLServerException: Login failed for user xxxxx

I created a simple database PersonInfo then I created user user1 password1 (SQL authentication). And after trying everything was unable to connect to the database.

I am using SqlServer2008 on Win 7, I’ve got the latest JDBC driver from Microsoft.

My code is:

import java.sql.*;

public class hell {
public static void main(String[] args) {
    
    try {
        Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver").newInstance();
Connection conn=  DriverManager.getConnection("jdbc:sqlserver://localhost:1433;databaseName=PersonInfo;user=Sohaib;password=0000;");


System.out.println("connected");
       }

    } catch (Exception e) {
        e.printStackTrace();
    }
}
}

Here’s the Exception

Exception: Unable to get connect
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'Sohaib'.
and all other supporting errors.

I ran into the same issue, and I fixed it by adding my windows username to SQL and then to my server, here is how I did:

First, create a new login with your Windows username:

Click Search, then type your name in the box and click check names.

Then add your that user to the server:

Right click on the Server > Permissions > Search > Browse > Select your user
(You will notice that now the user you created is available in the list)

I hope it helps

I got the same error message when trying to connect to my SQL DB in Azure (using sql-cli). The simple solution was to escape the password with single quotes like this:

mssql -s server.database.windows.net -u user@server -p 'your_password' -d your_db -e

answered Apr 19, 2017 at 15:19

answered Aug 16, 2017 at 7:55

I have also caught the same issue,But don’t worry the solution is so simple

We need to understand the basic terms first that this error “Login Failed for User (Microsoft SQL Server, Error: 18456)” means you entered invalid credentials when logging into SQL Server with specific server authentication type.

Where I have Selected the option of Windows Authentication mode in Server Authentication

and In my ConnectionString in appsettings.json file has the following connection string:

Server=DESKTOP-PK4BJF5;Database=lms;Trusted_Connection=false;MultipleActiveResultSets=true;TrustServerCertificate=true

In which the «trusted-connection» is a parameter used in database connection strings to specify the type of authentication to be used when connecting to a database server.

When «trusted-connection» is set to «true» or «SSPI» (Security Support Provider Interface), it means that the connection will use Windows Authentication to authenticate the user. This means that the credentials of the currently logged-in Windows user will be used to connect to the database server. This type of authentication is also sometimes referred to as «integrated security».

When «trusted-connection» is set to «false», it means that the connection will use SQL Server Authentication to authenticate the user. This means that the connection string will contain a user ID and password that are used to connect to the database server.

I am Updating the Connection String line and just write SSPI instead of /false

"Server=DESKTOP-PK4BJF5;Database=lms;Trusted_Connection=SSPI;MultipleActiveResultSets=true;TrustServerCertificate=true",

answered Apr 12 at 4:46

For Can not connect to the SQL Server. The original error is: Login failed for user 'username'. error, port requirements on MSSQL server side need to be fulfilled.

There are other ports beyond default port 1433 needed to be configured on Windows Firewall.

https://stackoverflow.com/a/25147251/1608670

answered Oct 24, 2017 at 19:32

answered Jun 5, 2018 at 18:46

Just in case any one else is using creating test users with their automation….

We had this same error and it was because we had recreated the user (as part of the test process). This caused the underlying SID to change which meant that SQL couldn’t properly authenticate the user.

We fixed it by adding a drop login command to our testing scripts to ensure that a previously created user (with the same user name) was no longer present on the instance.

answered Aug 4, 2020 at 6:23

answered Oct 31, 2020 at 16:38

In my case I have configured as below in my springboot application.properties file then I am able to connect to the sqlserver database using service account:

url=jdbc:sqlserver://SERVER_NAME:PORT_NUMBER;databaseName=DATABASE_NAME;sendStringParametersAsUnicode=false;multiSubnetFailover=true;integratedSecurity=true
    jdbcUrl=${url}
    username=YourDomain\$SERVICE-ACCOUNT-USER-NAME
    password=
    hikari.connection-timeout=60000
    hikari.maximum-pool-size=5
    driver-class-name=com.microsoft.sqlserver.jdbc.SQLServerDriver

answered Jan 11, 2021 at 22:44

try using this connection string

Server=ServerName;Database=DbName;Trusted_Connection=SSPI;MultipleActiveResultSets=true;TrustServerCertificate=true

answered Jan 3 at 16:04

answered Feb 18, 2019 at 7:33