Post reply

Login failures causes

  • May 26, 2016 at 8:11 am

    #308000

    To All,

    Recently, we moved 2 databases from one server to another server. After that I am observing the login failures in the old server.

    But we didn't find any SQL Jobs that are running under that account. How can I identify which is using that account in the local machine?

    Login failed for user 'testuser'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]

  • May 26, 2016 at 8:18 am

    #1881565

    seen that error before.

    you don't have to investigate any jobs, just fix the login.

    the default database for the logins does not exist.

    so if I migrated the login mydomain\Lowell with a default database of [Sandbox], if sandbox does nto exist, I fail at the login.

    change the logins default database to master.

    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!

  • May 26, 2016 at 8:21 am

    #1881570

    If you run a trace to capture failed logins, you'll get all sorts of extra information, such as the name of the application that's trying to connect (if the application specifies its name in the connection string). But it must be something that was connecting all along, and is only failing now because the database has been pulled away from under it. You'll need to consult the documentation for the application that uses the database, or speak to the people that support it.

    John

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

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