"SA" Landing failed SQL Server error 18456 workaround

You can still log on by using a Windows account.

The process of locating the problem:

The first step: Start all the SQL-related services, the problem remains;

Step two: Look at Windows Firewall, which is started by default and does not start the selection by disabled. Two tips "Because of security considerations, some settings are controlled by Group Policy" "Windows Firewall is using your domain settings". First use Gpedit.msc to play Group Policy Editor, machine configuration--Management template--network--Network connection--windows Firewall--standard configuration file, see the right option properties, are not configured, the problem is not here.

Another tip mentions domain settings, domain settings cannot disable SQL Server, and I look at the local open port (Netstart-an), and 25,1433,1434 are all development states.

Halo, will it be a wrong password?

The third step: I login with Windows account, after the successful connection, select "Properties",

Right-click an instance, and in the Properties window, go to the security key to see that the settings in Server Authentication are SQL Server and Windows Authentication mode.

Then execute the following statement to enable the SA user and change the sa password

EXEC sp_password ' sa ', null, ' sa '

ALTER LOGIN SA ENABLE

Error executing:

Message 15116, Level 16, State 1, line 1th

Password validation failed. The password is too short to meet Windows policy requirements.

Haha, the problem is found.

Local settings may be overridden by domain settings. The security policy is specified in the domain settings and the password must be somewhat complex. Change the sa password again,

EXEC sp_password ' sa ', ' uiop_098mn ', ' sa '

ALTER LOGIN SA ENABLE