How can a login simultaneously fail and succeed?

  • I can't get a user to be able to use our app. They're in an Active Directory group. I've added that AD Group as a login in SQL Server, made a User associated with that login and added the database to the securables.

    But in testing when I try to log in using a test account I get an error that says, "The underlying provider failed on Open. Login failed for user 'OURDOMAIN\Test_Mgr'".  But when I look at the current active error logs I see, "Login succeeded for user ' OURDOMAIN\Test_Mgr'".

    Huh??? I do not see how it is possible for the same action to simultaneously fail and succeed. Please, could someone help me with this paradox.

    Kindest Regards, Rod Connect with me on LinkedIn.

  • check that login's default database.
    see if the database has been dropped/removed, or the user no longer has access to that database. in those cases, setting the default database to master is probably the easiest fix.
    everyone has a limited access tot eh master database, it always exists for every login.

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • You're right, they did not have master as their default database. I had set it up and assigned it to the database we want them to run against. I just changed it and tested it right away, but it still gave the same error. Should I wait a while for it to work its way through?

    Kindest Regards, Rod Connect with me on LinkedIn.

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

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