Login fails after password reset or new user creation despite updating password in database

Open

#1,392 opened on May 19, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 15/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: sql
Domain: databases

Research direction

No repository file, test, or entry point is identified; start by determining whether this SQL Server login report applies to a sample in the repository rather than to local server configuration. Done would require a reproducible repository-specific failure and a named sample or test to change.

Written by the indexing model from the issue text.

Description

I am encountering a critical issue where I cannot connect to my SQL Server instance using the sa user, even after resetting the password via SQL Server Management Studio and after creating new users. The error message received is:

pgsql
Copy
Edit
Cannot connect to Mubashir.

The problem occurs when attempting to log in to SQL Server using the sa account.

Password reset attempts for the sa user have been performed both through the application and directly via SQL Server Management Studio.

New users have also been created with known passwords, but login attempts for those users fail as well.

The error corresponds to SQL Server error 18456, indicating login failure due to invalid credentials or possible permission issues.

The issue persists even after verifying that SQL Server services are running and that the login names exist.

No additional errors or messages are shown except the login failure notification.

I have reviewed Microsoft documentation for error 18456 but have not resolved the issue.

What I have tried so far:

Resetting sa password through SQL Server Management Studio.

Creating new SQL Server users with proper roles and passwords.

Checking SQL Server authentication mode (confirmed it is set to mixed mode).

Restarting SQL Server service.

Ensuring no network or firewall blocks.
@microsoft/mssql-server, @mattn, @brettcannon, @gregturn, @SqlChicken, @bradleyh

Dominant language: PowerShell
Stars: 11.2k
Forks: 9.1k
Avg merge: 2d 7h
Merged PRs (30d): 14

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Batched `completeJobs`/`failJobs` are never retried: the retry loop in `batch()` exits after the first failure Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

graphile/worker#636 · Opened Sep 21, 2026
Test Failure: com.ibm.ws.jdbc.fat.sqlserver.SQLServerTest J2CA0079E Open

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

OpenLiberty/open-liberty#35839 · Opened Sep 21, 2026
hash join v2: 'unsupported column type for pre-alloc 225' when joining on a VECTOR column Open

affects-9.0 found-by-ai may-affects-25.10 may-affects-26.3 may-affects-26.9 may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/major sig/execution type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

pingcap/tidb#71473 · Opened Sep 21, 2026
JSON_VALUE fails to parse when a RETURNING clause is present but the optional ON EMPTY/ON ERROR clause is omitted Open

Difficulty 1/5 Under an hour Newbie friendliness 92/100

antlr/grammars-v4#5014 · 1 comment · Opened Sep 21, 2026
readBinary(std::vector) throws a bare Poco::Exception (POCO_EXCEPTION code 1000) for too-large sizes instead of TOO_LARGE_ARRAY_SIZE Open

comp-query-execution fuzz

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

ClickHouse/ClickHouse#121303 · 3 comments · Opened Sep 21, 2026

More Databases issues