Error: 18456, Severity: 14, State: 58.

Question

Error: 18456, Severity: 14, State: 58.

robinsonir

Old Hand

Points: 346
More actions
September 23, 2010 at 12:59 pm

#387854

I am seeing the following error in the SQL ERRORLOG
2010-09-23 09:26:34.90 Logon Error: 18456, Severity: 14, State: 58.
2010-09-23 09:26:34.90 Logon Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: ***.***.***.***]
However the SQL instance is configured for MIXED mode authentication and the same ERRORLOG file confirms this
2010-09-23 09:25:25.05 Server Authentication mode is MIXED.
Has anyone come across this before?
There are a few weird things that just don't make sense to me
1. If I change the program getting the error from logging on with Windows authentication to SQL Server authentication it works just fine.
2. This program is a Windows service and the error occurs when the service is configured to run under the LocalSystem account. If I change it to run under a domain account it works fine
3. There is a 2nd service connecting to the same database, also running under LocalSystem, and that logs on just fine.
Needless to say I am a bit of a confused 🙂
BTW this is SQL 2008 R2
2010-09-23 09:25:25.05 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Thanks for any assistance
Ian

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

sturner SSC-Insane Points: 22411 More actions · Answer 1

I can't explain why you are getting that specific error message (I'd like to see your connection string), but you should always have a service run under a domain account or a local user account if it needs to access database and other outside resources. You should create a separate login for the account on the SQL server for the account the service is running as (or add the user account to a local or domain group).

The probability of survival is inversely proportional to the angle of arrival.

robinsonir Old Hand Points: 346 More actions · Answer 2

Thanks for your feedback. I would normally run the service under a domain account but in this particular case I was pulled in to troubleshoot the issue on a colleague's machine and that was how they had it set up. I am more concerned about the inconsistencies I'm seeing, i.e. SQL saying it is configured for Windows authentication only when it is clearly configured for mixed-mode and one service connecting as LocalSystem while another does not, and trying to understand why they are what they are.

Thanks again for taking a look.

sturner SSC-Insane Points: 22411 More actions · Answer 3

Like I said, it would be nice to look at the actual connection strings each is using, but the local "system" account is really sort of a non-entity and should not be used as a basis for SQL server access if you are concerned with security.

The probability of survival is inversely proportional to the angle of arrival.