Login Failure

  • I was wondering if anyone might have an idea of why i'm getting the following error:

    Login failed for user ' ]

    Error:18456, Severity:14, State:16

    The error began after we had an IT firm come in and move a number of databases to a new partition (d:) to open space on the local drive (c:). They used Detach/Attach to move the databases. The user is an SQL Login account and was orignally the owner of the databases. The owner is now a Windows login account; the one used to attach the databases after the move.

    Thanks for any help.

  • Hi,

    This seems to be a permission issue. The user does not have the permission to access the database. Can you add the user to that database. Also incase if you want the database owner to be changed as before...run the following commnad.

    use dbname

    go

    sp_changedbowner 'Ur SQL login'

    Incase if the sql login has the required permission, check to see if the default database setting for this database is not set to ' '. Change it to the correct database.

    Regards,

    Rajini

  • Thanks Rajini.

    There are a number of possible databases. Is there a way to determine which database(s) are the problems?

  • If the user isn't able to login, i don't believe it is a database permission problem (but more at an instance level). I would do the following

    1. Ensure user is a valid login (make sure the server is not case sensitive)

    2. Verify the default database of the user is available - change that to master (if not already)

    3. Finally you could reset the password for the account and try and login

  • I think I may have figured it out. Not all the databases have been reattached and the third-party software is still trying to access those databases (it uses the user account in the error message). Those databases aren't in use so no users would have told me the were having problems.

    Thanks for pointing me in the right direction and helping me figure this out. 😀

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

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