![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
| Date 12/23/2010 9:24:25 AM |
#2
| |||
| |||
|
|
If I query the database select getdate I get 2010-12-23 09:08:17.330 but I have entries in the Error log like (User name and server name edited) Date 12/23/2010 9:24:25 AM Log SQL Server (Current - 12/23/2010 9:24:00 AM) Source Logon Message Login failed for user 'xxx'. [CLIENT: <local machine>] |
#3
| |||
| |||
|
|
Mark D Powell (Mark.Powe... (AT) hp (DOT) com) writes: If I query the database select getdate I get 2010-12-23 09:08:17.330 but I have entries in the Error log like *(User name and server name edited) Date * * * * *12/23/2010 9:24:25 AM Log * * * * *SQL Server (Current - 12/23/2010 9:24:00 AM) Source * * * * *Logon Message Login failed for user 'xxx'. [CLIENT: <local machine>] That seems like something you have culled from Object Explorer. Am I right? I don't want to belittle you or anything, but did you double-check that the query window and Object Explorer are connected to the same server? -- Erland Sommarskog, SQL Server MVP, esq... (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx |
#4
| |||
| |||
|
|
Yes, I am certain that the posted information is for the same SQL Server since the messages were copied from the current SQL Server Error Log accessed via SQL Server Management Studio running on the database server. No other instances are configured to the tool. I just copied and pasted from the bottom of the log display, that is, I double clicked a log entry and copiled from the bottom portion of the window that SSMS opens. |
|
I have another 20 or so SQL Server installations running and I have never seen this issue on any of them. This installation is running under VM but then agains so are several of my other systems. |
#5
| |||
| |||
|
#6
| |||
| |||
|
|
Mark D Powell (Mark.Powe... (AT) hp (DOT) com) writes: Yes, I am certain that the posted information is for the same SQL Server since the messages were copied from the current SQL Server Error Log accessed via SQL Server Management Studio running on the database server. *No other instances are configured to the tool. *I just copied and pasted from the bottom of the log display, that is, I double clicked a log entry and copiled from the bottom portion of the window that SSMS opens. Well, you confirmed my assumption from where you got the message. Next time you see this, run xp_readerrorlog from the query window, and see if you can see the same error message. I have another 20 or so SQL Server installations running and I have never seen this issue on any of them. *This installation is running under VM but then agains so are several of my other systems. One possibility is that the clock had drifted, and just had been corrected. I don't know common this is with server-class VMs, but I remember I had severe problems with the time get very fast or slow in my VMs a couple of years back. I think the problem is related to power-saving features in the CPU and/or BIOS. -- Erland Sommarskog, SQL Server MVP, esq... (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx |
![]() |
| Thread Tools | |
| Display Modes | |
| |