June 27, 2024 at 2:56 am
This one confuses me. The server is set to mixed mode authentication and has been for years. Application team used to use a sql login but has just switched to a windows (Active Directory) group in which their service account is a member. SQL logins have been disabled but not yet deleted. I'm trying not to roll back this change. If the code were using the old SQL login, the error message would be "this login has been disabled." It's not.
They run their app and get login failures. I check the SQL log and get the below message. Please note I did not scrub the user name. Only the IP address. The rest of this message is what they get.
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Integrated authentication only. [CLIENT: xxx.xx.xx.xxx]
Error: 18456, Severity: 14, State: 58.
Error state 58 is for Windows authentication only or mismatched SIDS. But AD passes the SIDS down to SQL and the authentication mode definitely is mixed.
Any thoughts on this particular issue? Any place else I should check?
June 27, 2024 at 8:05 am
have you double checked the auth type on the instance to ensure it's still mixed mode.
If someone changed it and then a restart occurred down the line the new auth scheme would persist
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 27, 2024 at 1:01 pm
Yes. I triple-checked before I posted.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply