Post reply

Login failed for user 'joebloggsSQL@domainname.internal' Reason: Could not find a login matching the name provided

  • September 20, 2017 at 4:52 am

    #340171

    Hi 

    I am receiving this error message when a user tries to login:

    Login failed for user 'joebloggsSQL@domainname.internal' Reason: Could not find a login matching the name provided [Client: xx.xxx.xxx.x]
    Eroor 18456, Severity 14, State 5.

    It is a AD domain account that has the issues.

    The account is listed in security of the instance as

    domainname\joebloggsSQL    and has sysadm, public premissions etc.

    Any idea how to fix this issue?

  • September 20, 2017 at 5:52 am

    #1960136

    How is the user trying to login into the SQL Server? It sounds like it's trying to pass the user as "joebloggsSQL@domainname.internal", and possibly even trying to use SQL Authentication, rather than Windows/Integrated Authentication. If you use integrated security, the Login will always be passed in the format [Domain\Username], and the error in the logs will look like this:
    Login failed for user '[Domain\MyUsername]'. Reason: Could not find a login matching the name provided. [CLIENT: [My IP]]
    Error: 18456, Severity: 14, State: 5.
    The fact that the it says the user "joebloggsSQL@domainname.internal" cannot be found strongly suggests they aren't trying Windows Authentication and are using some other method.

    If they're using SSMS, for example, they just need to be logged in as themselves on the PC, or run SSMS as that user. Type in the Server Name (and Instance), and click Connect with the Windows Authentication selected in the drop down.

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

  • September 20, 2017 at 7:24 am

    #1960158

    @Thom A  -  that could well be the issue....for some reason this application is launching SSMS with sqlserver authentication for a windows account.

  • September 20, 2017 at 7:47 am

    #1960164

    caz100 - Wednesday, September 20, 2017 7:24 AM

    @Thom A  -  that could well be the issue....for some reason this application is launching SSMS with sqlserver authentication for a windows account.

    SSMS doesn't "launch" into SQL Server Authentication mode, you just need to select the authentication mode on the Connect Menu. So, as shown below, I'm using Windows Authentication (note my username has been removed):

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

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

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