This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 71%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECL%3C/text%3E%3C/svg%3E)
I deleted the window local account. Even though I re-created the window account using the same name,
this re-created window account cannot login the SQL server 2012 thru the SQL server . Error : 18456
Anyone know how to fix ?
Hi @calvin Lee , Welcome to Microsoft Q&A! Could you connect SQL Server with sa account? And you could check the error log to get more details about this error, to find the state for this error:
Hi @calvin Lee , did below answers could help you? Any update for this issue?
The login's Windows account SID, not the name, is used for authentication. A new SID is generated when a Windows account is recreated.
You'll need to drop the login (and db users, if any) and re-add it. If you have no other account you can use for this operation, follow the steps detailed in Connect to SQL Server when system administrators are locked out.
It is common to restore DB from one server to another server. The window account SID is different on the data restoration server.
It looks very trouble to drop and create login a/c after DB restoration on another server and also need to grant the DB object access right if needed .
Would there anyway to sync or remap the window a/c to the db users ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 23%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJW%3C/text%3E%3C/svg%3E)
A windows domain account does not change SID - a local windows account on each server would have a different SID. If you are using local windows accounts on each server - that is going to be problematic. There isn't any method of creating a windows account with a specific SID.
@calvin Lee , domain accounts will avoid the problem as @Jeffrey Williams mentioned. Windows authentication with local accounts is problematic because the local account on a different machine is a different account entirely and cannot be trusted.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 1%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
What is the purpose of this local Windows account? You normally do not use local Windows accounts to connect to SQL Server.
As others said, you should either use Windows Domain accounts, or SQL Logins (not recommended as not as secure). Using local Windows accounts is problematic.