SQL 2008 Error: 18456, Severity: 14, State: 58 incorrectly reports authentication mode
-
Monday, June 20, 2011 7:58 PM
The SQL 2008 SP2 x64 instance on Windows 2003 with mixed mode authentication reported the error:
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: xxx.xxx.xxx.xxx]
Error: 18456, Severity: 14, State: 58.I first suspectied a KERBEROS (SSPI Context) error because the user id came through as '' (reverting to NTLM and replacing the user id with blank). However, there were no windows event log messages indicating this was the issue.
After restarting the application, the errors went away.
What are possible root causes? Do I have a configuration item that I need to fix? Is this a bug in the error message?
All Replies
-
Tuesday, June 21, 2011 1:28 AMModerator
Hi ajsongy2,
Do you restart the SQL Server service after you changing the authentication mode? You need to restart it after this property changed. Please take a look at the article on BOL: How to: Change Server Authentication Mode.
In addition, I find another thread addressing this type of issue: http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/e1082cad-9248-44ed-bfcc-c08d7cc08831/.
Best Regards,
Stephanie Lv
- Proposed As Answer by VidhyaSagarModerator Wednesday, June 22, 2011 2:27 PM
- Marked As Answer by Alex Feng - MSFTMicrosoft Community Contributor, Moderator Thursday, August 04, 2011 10:30 AM
- Unmarked As Answer by Stephanie LvMicrosoft Contingent Staff, Moderator Friday, August 05, 2011 12:30 AM
- Unmarked As Answer by Stephanie LvMicrosoft Contingent Staff, Moderator Friday, August 05, 2011 12:30 AM
-
Monday, June 27, 2011 8:46 PM
Authentication mode was never changed. The error message was wrong. The fix was to re-start the application.
I was wondering what could have caused such an eroneous error message - if this is an indicator of a bigger issue
-
Thursday, August 04, 2011 5:44 AM
Hi ajsongy2,
I am facing same problem, can you guide me to resolve the issue.
Rajesh Ranjan
- Marked As Answer by Stephanie LvMicrosoft Contingent Staff, Moderator Friday, August 05, 2011 12:30 AM
- Unmarked As Answer by Stephanie LvMicrosoft Contingent Staff, Moderator Friday, August 05, 2011 12:30 AM
-
Thursday, August 04, 2011 7:32 AM
> I am facing same problem, can you guide me to resolve the issue.
Please start a new thread and relate your situation in full. Don't forget to include the complete error message.
Erland Sommarskog, SQL Server MVP, [email protected] -
Wednesday, April 25, 2012 9:58 AM
Such a buggy error has not been responded by any MSFT SQL team experts. If Microsoft experts do not help with this, where do we go?
I am having the same problem but not sure what to do. It could be related to Kerberos but I need to be sure before going to infrastructure admins:-(
Thanks
Chandan
.png){kind=spacer}
