login failed for user 'sa' because the account is currently locked out. the system administrator can unlock it

-

If the mixed mode authentication is enabled in SQL Server, you can log into SQL Server Management Studio with Windows Authentication, and then unlock any SQL Server user account easily.

Step 1: Open SQL Server Management Studio and select Windows Authentication to login.

Step 2: Go to Security -> Logins -> sa, and double click on sa account.

Step 3: After sa Login Properties dialog opens, select the General page, uncheck the box besides Enforce password policy, and click OK.

Step 4:Select the Status page, make sure the box besides Login is locked outis unchecked. Then the SA account can be unlocked and you can successfully connect to SQL Server with SA login.

Comments

  1. Veera Blogspot25 December 2020 at 23:30

    Great article,Thank you for sharing this valuable info with us.
    Keep updating...

    MSBI Training

    ReplyDelete

Post a Comment

Popular posts from this blog

Failed to execute the package or element. Build errors were encountered

-
Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package
Read more

Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)

-
TITLE: Microsoft SQL Server Management Studio ------------------------------ Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks) ------------------------------ ADDITIONAL INFORMATION: System.Data.SqlClient.SqlError: Exclusive access could not be obtained because the database is in use. (Microsoft.SqlServer.SmoExtended) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=12.0.2000.8+((SQL14_RTM).140220-1752)&LinkId=20476 ------------------------------ BUTTONS: OK ------------------------------ Procedure 1: 1. Right click Databases 2. Restore Database... 3. [General] Source from Device, select the bak file 4. [General] Change the Destination database name to a new name 5. [Files] Change mdf and ldf Restore As paths to a different, new path 6. [Options] (unnecessary on the other computer) Check Overwrite the existing database (WITH_REPLACE) 7. [Options] (unnecessary on the other computer) Chec...
Read more

On-premises data gateway December release

-
We are happy to announce that we have just released the December update for the on-premises data gateway (version 3000.154.3). This update brings the on-premises data gateway up to date with the December release of Power BI Desktop. Download:  On-premises data gateway December release This version of the gateway will ensure that the reports that you publish to the Power BI Service and refresh via the gateway will go through the same query execution logic/run-time as in the December version of Power BI Desktop.
Read more