Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
eroberts
Starting Member
4 Posts |
 Posted - 2010-03-05 : 16:13:23
|
| Suddenly started receiving a log full of login failed messages with Error: 18456, Severity: 14, State: 16.This happens for any login where the default db is not explicitly stated. Explicitly stating the default db in the connection works fine, but should not be required in a correctly working server (so long as the default db is correctly set).The users are using domain login AND access is granted by an AD group. The group has the default database attribute set, the default database is online, and the users have access to no other databases by membership in any other group.I've also tried to rule out schemas without owners and SQL Agent jobs referencing db's that don't exist. I remain baffled.Any ideas what I'm missing or how to troubleshoot this?Cheers, Eric Roberts |
|
|
SreenivasBora
Posting Yak Master
164 Posts |
Posted - 2010-03-05 : 16:35:38
|
| Have you verified the log size of TR? on which database You got this error? User DB or amster DB?With RegardsSR |
 |
|
|
eroberts
Starting Member
4 Posts |
Posted - 2010-03-05 : 16:39:12
|
| Logs are reasonable size (a few MB) which is appropriate for this db. Full backups are taken each evening which resets these files. This problem is occuring when users attempt to login to a user db and the default db is set to that user db, not master.Cheers,Eric |
|
|
|
SreenivasBora
Posting Yak Master
164 Posts |
Posted - 2010-03-05 : 16:41:19
|
| if it is not on PRODUCTION, Truncate the log and try. Please send complete log details in case any issues.With RegardsSR |
|
|
|
eroberts
Starting Member
4 Posts |
Posted - 2010-03-05 : 16:46:21
|
| One other point of note: this only happpens with AD groups. If I add the domain users to the db instead of the group and set the default db correctly, we can connect without specifying the database upon connection. |
|
|
|
eroberts
Starting Member
4 Posts |
Posted - 2010-03-05 : 17:03:16
|
| This db is in production, but we can take quite a bit of liberty with it. We just kicked everyone out, backed it up, and changed it to simple logging. We tried after each change in this process but nothing got rid of the error upon connecting. |
|
|
|
|
|
|
|
|
Error 18456, Severity: 14, State: 16