July 11, 2022 at 12:36 pm
Okay. This is an odd one that I can't quite figure out. I hope someone can advise.
A user was having issues logging into a server with a new AD account. One of my coworkers verified the login was part of windows groups which had access to the server. For kicks and giggles, I added the login individually on the server level and gave it permissions on the database. The user tried again and got another error (he's using IntelliJ, which I know nothing about).
Now the login is set to deny interactive login, so he doesn't have the ability to actually use it interactively. But he tried setting it in his application which should allow usage. And yet when I check the SQL Error Logs, I still see this wonderful error:
"Login failed for user 'ADBC'. Reason: Could not find a login matching the name provided. [CLIENT: IP address]"
Why would I be getting this error if I know for a fact that the login is on the server and the server / database login name matches the error message login? Thoughts?
July 11, 2022 at 1:26 pm
Quick thought, did you get the connection settings details from the user?
😎
This might be helpful:
July 11, 2022 at 1:30 pm
Yes and no. The user sent me screenshots of a different login that worked and getting information from him last week was like trying to chase a cat through an active parade route. Lots of tangents and not quite answering the questions I asked, even when I tried asking a simple question with only two answers.
But it occurred to me looking at the error that the user may have forgotten to including the domain. The error specifically says ADBC instead of Domain\ADBC. So that's got me reaching out to the user and verifying.
July 11, 2022 at 2:04 pm
Forgetting the domain was exactly the problem. Now we have an encryption message (the client isn't requesting encryption on encrypted database), but that's an entirely different issue.
Thanks for the help!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply