| Author |
Topic |
|
oneislandhop
Starting Member
6 Posts |
 Posted - 2004-06-08 : 22:37:03
|
| I am trying to find out why I have constant login failures for the SQL Server service account.Here is the situation: Windows 2000 Mixed mode network. SMS 2.0 with MSSQL 7.0 - both are on NT4 member servers. I have noticed in the SQL server logs that the DOMAIN\SQLServer account has constant login failures, once in a great while it will have success. I have not been able to figure out what is going on. How do I track what the SQL server is trying to do with this account. It is an account with domain admin privileges which also give it local machine admin privileges.Help!!!!I'm NOT a SQL geek! I'm NOT! I'm NOT! I'm NOT! |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-06-08 : 22:40:45
|
| What are the login failures. That would help.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
oneislandhop
Starting Member
6 Posts |
Posted - 2004-06-11 : 05:38:33
|
| Login failed for user DOMAIN\SQLServer'. is the only thing that is logged in the SQL logs. The server application log has this in it: Type: Information User: N/A Source: MSSQLServer Category: Logon EventID: 17055 Description: 18456: Login failed for user 'DOMAIN\SQLServer'.Data: (Hex deleted).H......Name of machine deleted for security purposes....m.a.s.t.e.r...Hope this helps, it doesn't do anything for me. the EventID 17055 is used for all events from the SQL server, logon/logoff/startup/shutdown/xpstar doing something/etc.I'm NOT a SQL geek! I'm NOT! I'm NOT! I'm NOT! |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-06-11 : 11:13:36
|
| Just for kicks, explicitly make it part of the local administrator group and see if this solves your issue.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
oneislandhop
Starting Member
6 Posts |
Posted - 2004-06-13 : 23:01:17
|
| It already is, and has been for quite some time..........I'm NOT a SQL geek! I'm NOT! I'm NOT! I'm NOT! |
|
|
|
oneislandhop
Starting Member
6 Posts |
Posted - 2004-06-17 : 04:41:54
|
| Is there anybody out there that can offer any further assistance??I'm NOT a SQL geek! I'm NOT! I'm NOT! I'm NOT! |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-06-17 : 09:48:19
|
| You need to put a trace on the server to capture errors and Security login failures. Find out where they are coming from. If you need help setting that up, let me know.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
oneislandhop
Starting Member
6 Posts |
Posted - 2004-06-20 : 03:19:21
|
| Yes, I would definitely appreciate the assistance. By 'trace' do you mean something like tcpdump?I'm NOT a SQL geek! I'm NOT! I'm NOT! I'm NOT! |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-06-20 : 05:12:35
|
| No, you need to use Profiler. This will provide you with the trace. For events you need to choose the failed logins and any errors. Monitor that and see what information it gives you. Have you used Profiler before?MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
oneislandhop
Starting Member
6 Posts |
Posted - 2004-06-21 : 02:51:42
|
| No, I have not used profiler before. I have seen references to it in the help files, though. Remember, SQL Server adminstration is not one of my strong points, even though I am learning more about it every day.I'm NOT a SQL geek! I'm NOT! I'm NOT! I'm NOT! |
|
|
|
pbnj130
Starting Member
1 Post |
Posted - 2004-06-23 : 13:46:49
|
| I was having the same problem with login failures. It turned out it was a ODBC SystemDSN connection and the login that it was logging in as didn't have full rights to the default database. I 1) went into Enterprise Manager, 2) right-clicked the default database->Properties->Permissions and checked all the boxes to give the login full rights.3) Restarted the SQLServer. You may want to try that and see if that works for you. Don't think it matters, but my SQLServer login was a SQLServer login, not Windows login. Here is my setup:Win2k ServerSQLServer 2000 w/ Mixed Mode Authentication |
|
|
|
keithc1
Yak Posting Veteran
88 Posts |
Posted - 2004-06-24 : 00:57:13
|
| First step is if you have sqlservice account as domain account with local admin privledges then make sure a Domain controller is indeed availeable to authenticate the service account. Next I would make sure that the password for the account was set to never expires cause if it did expire the service will not start. Another possibility could be corrupt registry in which case you can re-run setup and under advanced options choose registry rebuild. Also make sure your logged in with the account that registered the server just to be sureKeithc MCSE MCSA |
|
|
|
jhnegrao
Yak Posting Veteran
81 Posts |
Posted - 2007-01-24 : 12:30:20
|
| Hello, All!I'm having the same problem that was talked in this forum.I've started a trace using SQL Profiler and I got the following information during the Login Failure Event.EventClass: ExceptionTextData: Error: 911, Severity: 16, State: 1Anybody knows what's it?I got that this error has been caused by SQL Agent, because if I change the user that run the sqlagent, my log will be changed too.ThanksJuliano Horta |
|
|
|
|
SQL Server Service Account Login Failure