Hai,
I'm using SQL Server 2005 Standard Edition in my windows XP SP2 machine. I have only 1 server to which my 4 client machines are connected. Whenever I'm connecting to my SSMS using my domain account I get an error message indicating ' Login failed for user 'domain name account name '. (Microsoft SQL Server, Error: 18456). I have tried with Microsoft's KB Article ID: 889646 and all other kind of stuffs. It's not helping me to sort out this problem. Could anyone help me outta here.
Hai, I'm using SQL Server 2005 Standard Edition in my windows XP SP2 machine. I have only 1 server to which my 4 client machines are connected. Whenever I'm connecting to my SSMS using my domain account I get an error message indicating ' Login failed for user 'domain nameaccount name'.(Microsoft SQL Server, Error: 18456).I have tried with Microsoft's KB Article ID: 889646 and all other kind of stuffs. It's not helping me to sort out this problem. Could anyone help me outta here.
I can't seem to connect to our local instance of Microsoft SQL Server. I obtained the followinf infrotmation from the error log and I can't find anything in regards to Severity 14 and state 1. If anyone has any information in regards to this it would be much appreciated. Thanks in advance!
===================================
Cannot connect to 10.1.0.191.
===================================
Login failed for user 'kbober'. (.Net SqlClient Data Provider)
------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
I am trying to create a linked server between 2 SQL Server 2005 boxes. When I create the linked server I specify a login for the connection. The strange part is that I get the following error when it goes to test the connection:
The test connection to the linked server failed Login failed for user 'Domainuser'. (Microsoft SQL Server, Error: 18456)
I can use the SQL mangement studio to conenct to the database using this same login. The login has all the server roles assigned to it also.
Can anyone shed some light as to what may be the problem?
I just upgraded SQL Server 2000 to 2005 without any errors. Afterwards, I tried registering with sa and it failed. I registered with another sysadmin login to get into most of my databases, but I need sa to work for my backup software Idera SQLSafe to login to the database.
Does anyone have any experience or recommendations? I know my password is correct.
Please help I keep getting this message when I log on to my data base. Not sure what state 1 relates too
TITLE: Connect to Server ------------------------------ Cannot connect to <server_name> ------------------------------ ADDITIONAL INFORMATION: Login failed for user <user_name>. (Microsoft SQL Server, Error: 18456)
------------------------------ BUTTONS: OK ------------------------------ Server Name: <server~name>Error Number: 18456 Severity: 14 State: 1 Line Number: 65536
hi, i am getting the following error message while i am trying to login to the SQL Server 2005 on my vista laptop. i installed the server with dual authentication modes.
Login failed for the user'xxxx'(Microsoft SQL Server 2005. Error:18456)
if you have solution for my problem please send a reply as early as possible.
We are facing the error 18456 since we have changed our O.S from Windows 2000 to XP .When we try to check the ODBC connection it works with 2000 but with xp we still hve this error .Some people advise me to check the security options but I dit not find any that could explain this problem.
Since some days, i have this problem : i changed RTCcomponentService password, and now, when the SQL Server RTC service start (correctly, with network service), i have this log error message : Login failed for user 'CGAUPARTCComponentService'. [CLIENT: <named pipe>] ErrorReportingManager: Error raised, major=184, minor=56, severity=14, attempting to create sym
so, the service run with network (nt authority) correctly, but i have this error message. I think that the sql server database connect with rtccomponentservice old password. How I can change the password on this connection ? or what is de default password for RTCcomponentService ?
This is on SQL Server 2005 for the sa account. I am just looking the in the sql server error log.I know this is a password mismatch. Where is it mismatched? Does there have to be a 'sa' network user account now with 2005?
We are experiencing intermittent authentication errors "Error: 18456, Severity: 14, State: 10" on a customer's production server. This is a new server that has just been rolled out in the past several months. Rebooting the server appears to make the problem go away. We are using SQL authentication from a separate server that is running IIS. The application always uses the same username and password to connect.
Server info:
select @@version Microsoft SQL Server 2005 - 9.00.2047.00 (X64) Apr 14 2006 01:11:53 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
select @@version SP1
Sample error from SQL Server errorlog:
Date 7/7/2006 10:53:24 AM Log SQL Server (Archive #2 - 7/7/2006 12:20:00 PM) Source Logon Message Error: 18456, Severity: 14, State: 10.
MSDN (http://msdn2.microsoft.com/en-us/library/ms366351.aspx) lists various states for this error message but 10 is not included, and it says "Other error states exist and signify an unexpected internal processing error."
Note: This was not a case of a transient error that occurs only when SQL Server is starting up - these errors occurred at a variety of times, two months after the server was last rebooted / SQL Server last restarted.
I then try to run the same app from the client computer, it gives me:
Login failed for user 'LAPTOPGuest'.
After looking up the web for solution, I found that I can test the connection from the HOST computer in this way:
C:Documents and Settingskit>sqlcmd -E -S laptopsqlexpress 1> 2>
The test is successful
Now I run the same command on the CLIENT computer
C:Documents and SettingsKit>sqlcmd -E -S laptopsqlexpress Msg 18456, Level 14, State 1, Server LAPTOPSQLEXPRESS, Line 1 Login failed for user 'LAPTOPGuest'.
Now I can sure that from the client computer it cannot make a connection to it, then I look at the errorLog from my host computer
2006-08-13 21:41:00.34 Logon Error: 18456, Severity: 14, State: 11. 2006-08-13 21:41:00.34 Logon Login failed for user 'LAPTOPGuest'. [CLIENT: 192.168.0.5] 2006-08-13 21:45:10.64 Logon Error: 18456, Severity: 14, State: 11. 2006-08-13 21:45:10.64 Logon Login failed for user 'LAPTOPGuest'. [CLIENT: 192.168.0.5] 2006-08-13 21:48:41.80 Logon Error: 18456, Severity: 14, State: 11. 2006-08-13 21:48:41.80 Logon Login failed for user 'LAPTOPGuest'. [CLIENT: 192.168.0.5]
Now I know it is actually Error: 18456, Severity: 14, State: 11.
From this site : http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
11 and 12
Valid login but server access failure
It tells the connection string and SQL Express seem to be set up properly but the server access failed the remote connection
I have previously had SQL Server 2000 installed. I uninstalled SQL 2000 before I install SQL express but somehow the SQL Server Service Manager is still running at startup, and C:Program FilesMicrosoft SQL Server80 and its files are still exist after uninstallation..... Could this be a problem?
The Knowledge base suggestion on "enabling remote connection" is very simple and I do not understand why it is so difficult to me just to make a remote connection test work..... please, I need your help.
Recently, one of my clients began receiving this error. My team gave them sysadmin permissions, but this is terrible practice. I have read into disablying simple file sharing, but I don't even think I have the option to do it. I look in mycomputer > tools > view and don't see any option for this. Besides, the problem just started occuring recently, within the last week. The server is a cluster with veritas clustering and the edition is sql server 2000. Has anybody ever had a problem like this and have a good fix? Thanks for any help in advance... -Kyle
On localhost this application works fine but when I put on remote server. I am getting following errors. For both localhost and server, I am using same remote sql 2000. I will appreciate any help.
Thanks,
Arif
Server Error in '/' Application. --------------------------------------------------------------------------------
ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Data.Odbc.OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
I am not sure if th is is the right place to post this error but I am at my wits end on how resolve this problem My even viewer and log is logging this every min. This is happening on my MOSS 2007 production database server. I have been loooking on line and have not been able to find a concrete answer has anyone run into this problem and can you point me in the righ direction. Machine is Sql Server Standard win2003 Server service pack2
2008-05-14 19:46:00.66 Logon Login failed for user 'Domainuseraccount'. [CLIENT: <local machine>] 2008-05-14 19:47:00.66 Logon Error: 18456, Severity: 14, State: 16.
I finally got SQL Server 2005 installed on my Vista Ultimate computer and now I can't connect in SQL Server Management Studio.
I've got a named instance; use the built-in system account; windows authentication mode. I try to connect to
Server type: Database Engine Server name: RAYWOERNER-PCRAYWOERNER Authentication: Windows Authentication
and it fails. Please help.
Thanks,
Ray
Here are the technical details:
=================================== Cannot connect to RAYWOERNER-PCRAYWOERNER. =================================== Login failed for user 'RayWoerner-PCRay'. (.Net SqlClient Data Provider) ------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476 ------------------------------ Server Name: RAYWOERNER-PCRAYWOERNER 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.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server) at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
I am trying to connect to a remote SQL server via Management Studio. I am using the windows credentials I use to log into the computer but when I enter the same domainusername and password I get error 18456. I check the logs and see it is a state 6 error. After checking http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx I see that means Attempt to use a Windows login name with SQL Authentication
Is it possible for me to access a SQL server remotely?
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
I am using the Configure Publishing and Distribution Wizard in the SQL Server Enterprise Manager to configure a server as a Distribution and Publishing server. The security configuration on the server in question for authentication is SQL Server and Windows NT.
When I get to the first page in the wizard I select that I want to use the server as the Distributor. The other option is to use another server for the Distribution server - and this isn't what I want to do. The next page presents the option to use the default settings to configure the distribution databases or to configure the setup. If I select the default options I get the following error message when the arrow is pointing to Configuring Distributor:
---------------------------------------------- SQL Server Enterprise Manager could not configure 'SERVER1' as the Distributor for
'SERVER1'.
Error 18456: Login failed for user 'sa'. Remote logins for remote server 'repl_distributor' have been dropped. Server dropped. Server added. Server network name set.
----------------------------------------------
Something I have tried to change in order to fix this issue is the 'Replication agents on the Distributor log into the Publisher:' option from its default (By impersontating the SQL Agent account on 'SERVER1' (trusted connection)) to 'Using SQL Server Authentication of this account:', and in those fields I have put in 'sa' (which is a valid admin account to the SQL server) and the correct password.
In all cases I get the message above. Can anyone help me to see what I am doing wrong?
I have tried accessing a remote database in one of by stored procs using linked servers and also using OpenDataSource method. In both the cases , I am getting login failed error.
Following is the stored proc :
CREATE PROCEDURE TEST AS
SELECT * FROM OPENDATASOURCE( 'SQLOLEDB', 'Data Source=blrkec3432s;User ID=xyz;Password=xyz').LMC.dbo.STATE GO
This error has come up time and again and I can't seem to find a solution.
Specs: SQL Server 2005 v9.00.3054 on x64, Windows Server 2003 SP2
The user is a member of an active directory group. When he connects from his workstation via Management Stuidio, the error is:
Login failed for user '<domain><user>'. [CLIENT: xx.xx.xx.xxx]
I've dropped and re-created the login for the group, but to no avail. I've tried
SELECT * FROM sys.server_principals and I get a valid entry <domain>/<user> 81 0x0105... G WINDOWS_GROUP 0 2008-04-04 13:05:00.667 2008-04-04 13:05:00.673 <dbname> us_english NULL
I've verified that the user is a db_owner in the database and that this database is the default for the group.
I also tried SELECT endpnt.name,
suser_name(perms.grantee_principal_id) as grantee_principal,
and get Dedicated Admin Connection <domain><user> CONNECT SQL GRANT TSQL Local Machine <domain><user> CONNECT SQL GRANT TSQL Named Pipes <domain><user> CONNECT SQL GRANT TSQL Default TCP <domain><user> CONNECT SQL GRANT TSQL Default VIA <domain><user> CONNECT SQL GRANT
I am running SQL Server 2005 x64 SP2 and have problem connecting to database with the SQL logins I created. I test the database login using Microsoft ODBC Administrator to connect the the database locally, only 'sa' can login. All other sql logins I created fails and returns this message:
--------------------------- Microsoft SQL Server Login --------------------------- Connection failed: SQLState: '28000' SQL Server Error: 18456 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'doteasylogin'.
--------------------------- OK ---------------------------
In the SQL Logs, it shows: Error: 18456, Severity: 14, State: 12.
I have SQL 2005 Expess installed on Windows Server 2003 SP1.
My application is running as a service and is set to depend on SQL Server instance... During the startup my app attempts to connect to the databes and it fails to do so, after 30 retries (1second appart). SQL Server log has this error msg: Error: 18456 "Severity: 14, State: 10"
Once the server has started, I cam manually start my application and it then sucesfully opens a connection to the database.
i am new to sql server 2005 express. I am trying to set up xp embedded database. I am trying to allow remote access to a central xp embedded database. i have the database on the sql server machine.
i am using the component database manager toll on a remote machine so that i can connect to the remote xp embedded database. when i try to connect to the db through sql server i get the following error in the log file.
2006-09-12 17:15:10.18 Logon Error: 18456, Severity: 14, State: 11. 2006-09-12 17:15:10.18 Logon Login failed for user 'HOSTNAMEGuest'. [CLIENT: XX.XX.XX.XX]
where HOSTNAME is the hostname of the pc that sql server 2005 is running.
XX.XX.XX.XX is the ip address of the client which is running component database manager tool.
Error: 18456, Severity: 14, State: 16. Login failed for user 'PRIsqlservice'. [CLIENT: 172.16.9.2]
in the log repeated every 15 seconds or so. I am logged into the server as prisqlservice, I have started the sql server and sql server agent with prisqlservice and I can access databases and tables inside the Server Management studio. I have set up the login prisqlservice and given it dbo owner access to all databases.
I am in the process of upgrading from 2000 to 2005. I have installed a new sql server 2005, restored backups of databases from 2000. I have also converted all packages and uploaded those to the new server (although they all point to the 2000 server). I have imported the jobs, but all but one are disabled and the one that is enabled ran okay when I ran it manually.
I have researched and researched this issue, and none seem to apply to my specific issue.
This is an extract of my errorlog:
2006-12-20 16:23:16.95 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2006-12-20 16:23:16.98 Server (c) 2005 Microsoft Corporation. 2006-12-20 16:23:16.98 Server All rights reserved. 2006-12-20 16:23:16.98 Server Server process ID is 1780. 2006-12-20 16:23:16.98 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2006-12-20 16:23:16.98 Server This instance of SQL Server last reported using a process ID of 4532 at 12/20/2006 4:23:52 PM (local) 12/20/2006 9:23:52 PM (UTC). This is an informational message only; no user action is required. 2006-12-20 16:23:16.98 Server Registry startup parameters: 2006-12-20 16:23:17.00 Server -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf 2006-12-20 16:23:17.00 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2006-12-20 16:23:17.00 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf 2006-12-20 16:23:17.23 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2006-12-20 16:23:17.23 Server Detected 2 CPUs. This is an informational message; no user action is required. 2006-12-20 16:23:17.93 Server Set AWE Enabled to 1 in the configuration parameters to allow use of more memory. 2006-12-20 16:23:19.65 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 2006-12-20 16:23:22.07 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2006-12-20 16:23:23.21 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2006-12-20 16:23:23.48 Server Database Mirroring Transport is disabled in the endpoint configuration. 2006-12-20 16:23:23.79 spid5s Starting up database 'master'. 2006-12-20 16:23:25.01 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required. 2006-12-20 16:23:26.17 spid5s SQL Trace ID 1 was started by login "sa". 2006-12-20 16:23:26.37 spid5s Starting up database 'mssqlsystemresource'. 2006-12-20 16:23:27.93 spid9s Starting up database 'model'. 2006-12-20 16:23:27.95 spid5s Server name is 'KSDBT01'. This is an informational message only. No user action is required. 2006-12-20 16:23:29.06 spid9s Clearing tempdb database. 2006-12-20 16:23:29.54 Server A self-generated certificate was successfully loaded for encryption. 2006-12-20 16:23:29.62 Server Server is listening on [ 'any' <ipv4> 1433]. 2006-12-20 16:23:29.62 Server Server local connection provider is ready to accept connection on [ \.pipeSQLLocalMSSQLSERVER ]. 2006-12-20 16:23:29.62 Server Server local connection provider is ready to accept connection on [ \.pipesqlquery ]. 2006-12-20 16:23:29.64 Server Server is listening on [ 127.0.0.1 <ipv4> 1434]. 2006-12-20 16:23:29.64 Server Dedicated admin connection support was established for listening locally on port 1434. 2006-12-20 16:23:29.68 Server SQL Server is now ready for client connections. This is an informational message; no user action is required. 2006-12-20 16:23:32.56 spid9s Starting up database 'tempdb'. 2006-12-20 16:23:32.67 spid13s Starting up database 'msdb'. 2006-12-20 16:23:32.67 spid12s Starting up database 'test'. 2006-12-20 16:23:32.67 spid14s Starting up database 'bravoAztecnology'. 2006-12-20 16:23:32.67 spid15s Starting up database 'bravoKNE'. 2006-12-20 16:23:32.67 spid16s Starting up database 'bravoKNS'. 2006-12-20 16:23:32.67 spid17s Starting up database 'bravoKNSBelgium'. 2006-12-20 16:23:32.68 spid18s Starting up database 'bravoKNSCanada'. 2006-12-20 16:23:32.68 spid19s Starting up database 'bravoKNSEngland'. 2006-12-20 16:23:34.79 spid20s The Service Broker protocol transport is disabled or not configured. 2006-12-20 16:23:34.81 spid20s The Database Mirroring protocol transport is disabled or not configured. 2006-12-20 16:23:35.01 spid12s Starting up database 'bravoKNSKennedy'. 2006-12-20 16:23:35.20 spid17s Starting up database 'bravoKNSSuperior'. 2006-12-20 16:23:35.35 spid13s Starting up database 'bravoKNSSuperiorSS'. 2006-12-20 16:23:35.48 spid19s Starting up database 'stamp'. 2006-12-20 16:23:35.83 spid20s Service Broker manager has started. 2006-12-20 16:23:38.59 spid14s Starting up database 'KNSSpecial'. 2006-12-20 16:23:39.31 spid18s Starting up database 'knsRPCS'. 2006-12-20 16:23:39.39 spid14s Analysis of database 'KNSSpecial' (16) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required. 2006-12-20 16:23:43.03 spid5s Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required. 2006-12-20 16:23:43.03 spid5s Recovery is complete. This is an informational message only. No user action is required. 2006-12-20 16:23:50.95 spid51 Using 'xpsqlbot.dll' version '2005.90.1399' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required. 2006-12-20 16:23:55.85 spid51 Using 'xpstar90.dll' version '2005.90.1399' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required. 2006-12-20 16:23:57.10 spid51 Using 'xplog70.dll' version '2005.90.1399' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required. 2006-12-20 16:24:00.02 Logon Error: 18456, Severity: 14, State: 16. 2006-12-20 16:24:00.02 Logon Login failed for user 'PRIsqlservice'. [CLIENT: 172.16.9.2] 2006-12-20 16:24:00.06 Logon Error: 18456, Severity: 14, State: 16. 2006-12-20 16:24:00.06 Logon Login failed for user 'PRIsqlservice'. [CLIENT: 172.16.9.2] 2006-12-20 16:24:01.06 Logon Error: 18456, Severity: 14, State: 16. 2006-12-20 16:24:01.06 Logon Login failed for user 'PRIsqlservice'. [CLIENT: 172.16.9.2] 2006-12-20 16:24:01.07 Logon Error: 18456, Severity: 14, State: 16. 2006-12-20 16:24:01.07 Logon Login failed for user 'PRIsqlservice'. [CLIENT: 172.16.9.2] 2006-12-20 16:24:03.84 Logon Error: 18456, Severity: 14, State: 16. 2006-12-20 16:24:03.84 Logon Login failed for user 'PRIsqlservice'. [CLIENT: 172.16.9.2] 2006-12-20 16:24:03.85 Logon Error: 18456, Severity: 14, State: 16. 2006-12-20 16:24:03.85 Logon Login failed for user 'PRIsqlservice'. [CLIENT: 172.16.9.2] 2006-12-20 16:24:03.96 Logon Error: 18456, Severity: 14, State: 16. 2006-12-20 16:24:03.96 Logon Login failed for user 'PRIsqlservice'. [CLIENT: 172.16.9.2] 2006-12-20 16:24:03.98 Logon Error: 18456, Severity: 14, State: 16. 2006-12-20 16:24:03.98 Logon Login failed for user 'PRIsqlservice'. [CLIENT: 172.16.9.2] 2006-12-20 16:24:41.41 Logon Error: 18456, Severity: 14, State: 16. 2006-12-20 16:24:41.41 Logon Login failed for user 'PRIsqlservice'. [CLIENT: 172.16.9.2] 2006-12-20 16:24:41.41 Logon Error: 18456, Severity: 14, State: 16. 2006-12-20 16:24:41.41 Logon Login failed for user 'PRIsqlservice'. [CLIENT: 172.16.9.2]
I am running SQL Server 2005 SP2 on Windows Server 2003.
I am continously geting below error.Please tell me how to avoid this error.and How I can supress this error popping into error logs?
Date 3/31/2008 8:46:58 AM Log SQL Server (Current - 3/31/2008 8:48:00 AM)
Source Logon
Message Error: 18456, Severity: 14, State: 11.
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. [CLIENT: xx.xx.xx.xx]
I am not using any linked server or replication.I have Sharepoint services connecting to this database.I want to learn step to troubleshoot this error.I have gone through many link during search but not found anything relevant.
Can you please suggest me troubleshooting steps so I can narrow down this problem and solve it.
