Login failed for User (Microsoft SQL Server, Error:18456)

Hi,
I am using SQL SERVER 2008. I was login through Windows Authentication and Unknowingly I have
deleted admin user (With name of my Computer e.g. "ABC-PC\ABC" ) under security=>Logins and restarted the SQL Server.
Now I am not able to connect to server using Windows as well as SQL Server Authentication Mode.
Please help me How can I create the same User again?
OR How can I connect to server using Windows or Sql Server Authentication??

as
you confirmed its sql 2008 , you have only below choices :
you
can ask anyone who manages/developer
who installed this server
your DBA should be able to help

Similar Messages

How to fix Login failed for user ''. (Microsoft SQL Server, Error: 18456)in windows 2008?

Hi All,
we are facing the Login fails issue .
how to resolve the bellow error , could you please suggested the possible ways .. ASAP
TITLE: Connect to Server
Cannot connect to ..
ADDITIONAL INFORMATION:
Login failed for user ' domain\name'. (Microsoft SQL Server, Error: 18456)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
BUTTONS:
OK
Log Name: Application
Source: MSSQLSERVER
Date: 10/6/2011 1:56:28 PM
Event ID: 18456
Task Category: Logon
Level: Information
Keywords: Classic,Audit Failure
User: domain\name
Computer:
Description:
Login failed for user ' domain\name'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
RAM

I was hitting myself in the head with this problem for a couple of minutes.... Everything was fine on the DC and Domain itself.. I added the Domain admins Group Principal for which I am part of... I was getting this error ... Long History... Short
(Right Click and Run as Administrator took care of this for me..) UAC was the cause of the problem.
Cannot connect to XX-DB-XX3.
===================================
Login failed for user 'XXXXS\XXas'. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
Server Name: XX-DB-XX3
Error Number: 18456
Severity: 14
State: 1
Line Number: 65536
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Cannot connect to SERVER. Login failed for user 'DOMAIN\user'. (Microsoft SQL Server, Error 18456) - SQL Server 2012 on Windows Server 2008 R2

I've seen multiple blogs and forums with similar problems and SQL 2012 or 2008. But no solutions that work for me.
I have installed SQL Server in mixed mode (SQL and Windows authentication). I can create new Login accounts in either mode. However, I cannot get an AD security group Login account to work. I am trying to add group 'DOMAIN\Domain Admins' or 'SERVER\Administrators'
as a Login so that any of the domain's administrator accounts can open SQL Server Management Studio and act as an 'sa' account on this server.
I have deleted the SQL account 'DOMAIN\Domain Admins'.
I have restarted SQL.
I have restarted the Win2K8r2 server.
I have launched SSMS as Administrator from the desktop of SERVER.
I have launched SSMS as another user (and used 'DOMAIN\user' to lauch it) from the desktop of SERVER.
I can create a login account named 'DOMAIN\user' (who happens to be a member of the 'DOMAIN\Domain Admins' group) and give this account 'sa' security, and when I do that, this account works as expected...
How do I add a security group as a Login account and give all members of that group the ability to be an 'sa' account?

Hi geoperkins,
Are you getting the following error message?
Error: 18456, Severity: 14, State: 11
Login failed for user <Domain\user>. Reason: Token-based server access validation failed with an infrastructure error.
If that is the case, the issue could be due to that the Windows login has no profile or that permissions could not be checked due to UAC. Please disable UAC firstly and check if it is successful to log in SQL Server.
Another reason could be that the domain controller could not be reached. You may need to resort to re-creating the login. Create a new group in AD, add users to the new group, then add the group to the local admin group and create login for the group in SQL
Server.
There is a connect item describing similar issue for your reference.
https://connect.microsoft.com/SQLServer/feedback/details/680705/cant-login-to-sql-using-windows-authentication-when-user-is-in-a-domain-security-group
For more details about above error, please review the following blog.
http://sqlblogcasts.com/blogs/simons/archive/2011/02/01/solution-login-failed-for-user-x-reason-token-based-server-access-validation-failed-and-error-18456.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Reports successfully execute but generate a login failed for user 'sa' err

I am running Crystal Reports Server XI R2. Classic ASP is used to generate embedded reports within our application. The crystal reports use ODBC to connect to a SQL Server 2005 database. The reports successfully generate in our Classic ASP application. However in SQL Server 2005, the following error messages are being generated each time a crystal report is ran:
- Login failed for user 'sa'.
- Error: 18456, Severity: 14, State: 8.
We know that we are passing the correct username/password to the crystal reports, becuase they execute successfully.
It appears that when the report is called, Crystal Reports appears to conect to SQL Server using a username/password that we didn't provide it at execution time, this fails and the SQL Server 'login failed for user' is generated. Then it runs the report using the username/password we provide and it successfully generates a report.
I have ran Profiler against the SQL Server Database and the 'Login failed for user 'sa' ' errors have a ApplicationName of either 'Seagate Crystal Reports' or 'Crystal Reports'. Therefore I know it is Crystal Reports generating these errors in SQL Server.
Does anyone have any ideas on how to stop these SQL Server 'Login failed for user 'sa' ' errors being generated?

What happens if you use Profiler when running the report using Crystal Report Designer?
If the report is ran through Crystal Report Designer, NO 'Login failed for user' error messages appear in profiler. Everything looks ok when ran in Designer.
Also, need to know what patch level you are on?
We are running Crystal Reports Server XI Release 2, Version: 11.5.8.8265
No additional patchs have been applied since Crystal Reports Server was installed.
We may try the SA account if one of the connections fail to log on with the credentials you provided. Verify the user you logged on with has rights to all tables.
The reports were running through our application using the SA account. The SA account has permissions to these tables. The reports do generate results and appear perfectly fine in the application. The issue is that when our application requests the report from Crystal Reports Server. Crystal Reports Server delivers the correct report to our application. However during the process to generate the report, 'login failed for user 'sa' ' errors are being generated in SQL Server 2005.
Also, I have tried creating a completely new SQL user called 'crystaluser'. I ran the report using Crystal Report Designer and used the crystaluser logon and saved the report. Then I ran the same report through our application. SQL Profiler will then display 'login failed for user 'crystaluser''.
Its seems as though Crystal Reports Server is first executing the report using the default SQL user saved with the report, but is either sending a blank password or no password at all. This generates the 'login failed for user' in SQL Server 2005. But it then uses the SQL username/password my application gives it and successfully generates the report. Of course this is only speculation.

[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'

Hi,
We have exadata x3-2. I am seeing this error in alert log file frequently.
The db version: 11.2.0.3 On RAC on Linux 5.8 x86-64Bit
Errors in file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
The file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc
Contains many repeated lines like below
*** 2015-01-21 06:34:40.209
ERROR, tran=21.24.51311, session#=1, ose=0:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
Could any please help why is this happening.
Thanks

Hi,
You have customers who are running distributed transactions using a gateway which need to be rolled back. However, the gateway has not been correctly configured for distributed transactions. To roll back a transaction on the SQL*Server database a connection is made as the user defined in the parameter HS_FDS_RECOVERY_ACCOUNT in the gateway init<sid>.ora file but this user has not been created in the SQL*Server database with the password defined in HS_FDS_RECOVERY_PWD. This user also needs to own the transaction log table.
I assume you are using the Database Gateway for SQL*Server (DG4MSQL) as the Database Gateway for ODBC (DG4ODBC) doesn't support distributed transaction.
If you have access to My Oracle Support have a look at this note -
How to Setup DG4MSQL to Use Distributed Transactions (Doc ID 227011.1)
Otherwise, check the Gateway documentation.
Regards,
Mike

Cannot connect to newly created SQL 2008 R2 instance. Login failed for user...

I'm not a SQL guy, just figuring my way around here...
I just created a new instance on an existing SQL server. The original instance works fine. On
Database Engine Configuration > Account Provisioning
I selected Windows authentication mode and added several users, myself among them.
Tried to log in with one my account and getting:
TITLE: Connect to Server
Cannot connect to SERVERNAME\INSTANCE.
ADDITIONAL INFORMATION:
Login failed for user 'domain\myusername'. (Microsoft SQL Server, Error: 18456)
Guidance/suggestions?
Thanks,
Scott

http://sqlserver-help.com/2014/07/08/help-how-to-find-cause-of-login-failed-for-user-error/
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

"Login Failed for user" in Standard Report Creation Wizard

I am trying to create a report using the report wizard in CR 08. When I choose new connection ==> OLE DB(ADO)==>Microsoft OLE DB Provider for SQL Server and enter the Server and user ID (no password), I get the error "Login failed for users".
SQL State: 42000
[DataBase Vendor Code: 18456]
I was using CR 10 and called the 1-866 # and was told to try it wil CR 08 and Im getting the same error. I know the log on information is correct because I use the same server name and userID to login with SQL Server management studio and Visual Studio 08.
Please let me know what I can do to link CR to my SQL Database.
Thanks,
John

How is your user accessing the site?
Did you extend it to a different zone, and if so what authentication provider are you using for that zone or is it the same zone?
Looks like the domain is a workstation name? are they logging in with valid credentials for the WIN-IMH9QUCN1FU workstation, which may be different than what they usually log in as?
ieDaddy
Blog: http://iedaddy.com
Twit: @iedaddy

Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' between sql server 2005 32 bit and sql server 2012 64 bit

Hi All,
Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account.
'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Appreciate your quick response.
Vikas.M.S

Hello,
Please read the following resources:
http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server Agent job between 2 instances fails with Error 18456 - Login Failed for user

Hi,
SQL Server version: 2012 EE
OS: Windows 2008 R2 Enterprise
In my server, i have 2 instances, and I am trying to configure a SQL Server Agent job to query one table in Instance A, and insert some modified data in Instance B, both in the same server.
When i execute the job in instance A, i get the following error:
Executed as user: NT SERVICE\SQLSERVERAGENT. Login Failed for user "NT SERVICE\SQLSERVERAGENT". [SQLSTATE 28000] (Error 18456). The step failed.
I have already configure instance A as Master and disabled encryption, by changing the parameter MsxEncryptChannelOptions to 0 in regedit. I've also made my target instance (instance B) as a Target.
What am i missing?
Thanks for your attention and pacience

Hello,
The NT SERVICE\SQLSERVERAGENT (virtual) account is not available on the other as you just mentioned. That is the reason for the login
failed error. Try using a Windows login as the
SQL Server Agent service account in both servers, the same Windows login (not a virtual account), and run jobs as the “sa” account.
http://msdn.microsoft.com/en-us/library/ms345578.aspx
You can also try a proxy account.
http://technet.microsoft.com/en-US/library/ms190698(v=SQL.105).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

MS SQL 2008 R2 Named instance: Login failed. Microsoft SQL server, Error: 18452) - Tryig to access using the FQDN assigned for the backup network card.

Hi,
I have a windows 2008 R2 Enterprise servers with standalone MS-SQL 2008 R2 named instance. The server is having two networks, once production and the second for backup. The server FQDN is resolving to the production IP. The backup NIC
DNS dynamic update is disabled and an "A" record is registered with the dns. While trying to connect to the instance using the management studio:
Successfuly able to connect using the instance name, the production hostname, production IP and backup IP.
but while trying to connect to the insance using the backup hostname getting the below error:
"Login failed. The login is an untrusted domain and cannot be used with windows authentication. (Microsoft SQL server, Error: 18452) "
This is required for the backup tool to get connected using the backup FQDN of the server.
Should I need to create a host name alias, request you to kindly assist me with the best recommedation to fix this.
http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspx

Hi,
It might be a kerberos issue. Check that there are valid SPN's registered using the setspn utility - http://technet.microsoft.com/en-us/library/cc731241.aspx
Thanks, Andrew
My blog...

Event 3351, SQL database login for 'DB_Config' on instance failed. Additional error information from SQL server is mentioned below. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

category-database
event id-3351
source-sharepoint foundation
SQL database login for 'DB_Config' on instance 'DB\instance' failed. Additional error information from SQL Server is included below:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I have been getting this error every hour on only 1 application server of the 2.
My farm consists of 2 app servers, 2 wfes & 2 sql nodes.
My public site is working fine. Authentication is NTLM.
SharePoint VSS Writer is disabled.None of my appPool accounts are running under local system.
I have read many forums/blogs, but couldnt find a solution for this.
Any help would be appreciated!

Hi,
As I understand, you found event id 3351 in event log. Please collect more information as below：
Check if the error also occurs on other servers in your farm.
Check if backup job is scheduled at the time when the event id occurs.
Please run Config Wizard or psconfig.exe -cmd secureresources on all servers and test the issue again.
Regards,
Rebecca Tu
TechNet Community Support

Sql Server 2012 Login Failed for user "NT Authority\System"

I have installed SQL Server on a new server. I have been getting the following error on each of the database in it.
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ABC'. [CLIENT: xxx.xxx.xxx.xxx]
Here is some information on the instance:
1) Default instance
2) SQL Server, Sql Server Agent, Sql Server Reporting services are running / log on using a domain service account.
3) Sql Server Browser is disabled.
4) SQL Server VSS Writer is running / log on as Local Service.
5) NT AUTHORITY\SYSTEM does exists in Login with just public server roles.
I ran a trace on login failed and I get:
ApplicationName: Microsoft Windows Script Host
and it runs every 15 minutes.
Help please?

Hi,
The error was thrown when the SCOM components connected to the backend SCOM databases.
You can specify a domain account, grant it the sysadmin role and the error should be gone.
Also, see the replies in your previous thread:
http://social.technet.microsoft.com/Forums/en-US/23f6b6cb-ec41-4117-8613-26d24c948827/login-failed-for-user-username-reason-failed-to-open-the-explicitly-specified-database
Thanks.
Tracy Cai
TechNet Community Support

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection

"[DBNETLIB] Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"
After patches applied on patch Tuesday the database reports the above error.
All accounts are domain accounts and SQLServer uses Windows auth.
DCDIAG show no errors
All servers and DC have been restarted,
Message in db log confirms the connection is being denied due to trust.
Event log shows same rejection
Protocols enabled: named pipes, tcpip, memory
TESTS:
PortQry: "
TCP port 1433 (ms-sql-s service): LISTENING"
Connect with domain admin accounts works from multiple clients systems to DB.
Cannot connect with newly created domain admin account
Can connect if new admin account connect to server in terminal server session and uses UDL wizard or any other tool including isql.
New standard user also fails to connect.
NOTES:
I removed the SSL patch and the IE security update to see if that was an issue.
¯\_(ツ)_/¯

Has someone left the company or has an account of some nature been dropped/replaced?
Please click "Mark As Answer" if my post helped. Tony C.
Hi Tony,
Srry but No. We just installed the monthly updates.
I went back and found I had missed removing a patch. I missed the rollup for Windows Server 2003:
Event Type: Information
Event Source: NtServicePack
Event Category: None
Event ID: 4382
Date:  3/12/2015
Time:  12:26:04 PM
User:  NETTEST\admin
Computer: DATA1
Description:
Windows Server 2003 KB954920 was removed from your computer, and the previous Windows Server 2003 configuration was restored.
After I removed that is still didn't work but after about five minutes it started working.
I guess I ned to report that to MS after I research what might be changed to make the patch work.
Every time I get stuck and ask for help it seems to be just before I stumble on the solution.
Thanks for replying.
Well - maybe this will help someone else.
Thanks again for replying Tony
¯\_(ツ)_/¯

Non-SysAdmins get error 18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.

I have a SQL 2008 R2 system (10.50.4000) where I'm having problems connecting any user that is not a SysAdmin. Example: I setup a new SQL Login to use Windows Authentication and grant that user db_datareader on the target database. The user attempts
to connect using Excel client or Access or SQL Management Studio and receives Error 18456. The SQL Server Logs shows Error 18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
The strange part is that if I temporarily grant the user the sysadmin server role then the user can connect successfully and retrieve data. But, if I take away that sysadmin server role then the user can no longer connect but again receives the Error
18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
We've turned off UAC on the client machine to see if that was the problem, but no change.
I have dropped and re-added the user's SQL Login (and the related database user login info). No success.
The Ring Buffers output shows:
The Calling API Name: LookupAccountSidInternal
API Name: LookupAccountSid
Error Code: 0x534
Thanks for any help.
-Walt

Yes, you understand correctly. The user is logging onto a workstation (not the server) with a Windows Authenticated id. The user is using either Excel or Access or SSMS and connecting to the server using a Windows Authenticated SQL Login account.
If the account has sysadmin role (which is only for testing) then the connection is successful. If I take away sysadmin role from the account then the connection is unsuccessful and the SQL Server Log shows Error
18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
(SQL Authentication is not an option here. I must use Windows Authentication).
Any other troubleshooting assistance you can offer would be appreciated. Thanks.
-Walt

Receiving error message "Login failed for user 'NT AUTHORITY\SYSTEM'" every minute on server which is the mirror

Hello,
I have 2 SQL Server 2008 R2 machines that are configured with database mirroring (using certificates as authentication), there is no witness configured. My issue is that the mirror server is receiving at least one of the below pared messages every
second and filling up my sql error log quickly.
SYSTEM is the service account user for the MSSQLSERVER service.
[298] SQLServer Error: 4060, Cannot open database "<databasename>" requested by the login. The login failed. [SQLSTATE 42000]
[298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\SYSTEM'. [SQLSTATE 28000]
The database has a status of: Affected database state is: Mirror, Synchronized/Restoring...
When I checking the database mirror monitor, it shows that its mirroring ok and everything has green checkboxes.
Is there a way to stop all these errors being logged, I'm assuming this isn't normal.
Marcus

Yes i have faced the same issues and tried everything and nothing was using this account, system was ended up with creating few GB's sql error log files everday.. and finally i had two options, 1 -- Rebuild the instance completely 2. Change the SQL Server
Audit settings to Only successful logins and restart the instance.. ( May be your current sql server level Audit setting is set to Failed & Successful logins..
Remeber my server was a DR so I have changed the SQL Server Audit settings to only Successful logins.. but production servers we will monitor both... :)
Raju Rasagounder Sr MSSQL DBA

Login failed for User (Microsoft SQL Server, Error:18456)

Similar Messages

Maybe you are looking for