Post reply

Login failed for user "Domanin\SPS_xxx_Config" Error: 14 State: 16

  • March 25, 2009 at 1:45 pm

    #219424

    Login failed for user "Domain\SPS_xxx_Config" Error: 14 State: 16

    We are testing MOSS 2007 database upgrade from 2000 to 2005 (different machine), after the restore, the web front end can't connect to the newly restored/upgraded 2005 database. Logins were recreated in the new 2005 database so mo orphan users exist in the 2005

    database. This account is a SPS admin account, it has been granted sysadmin privilege at the SQL server server level and also added to the local admin group on this Windows 2003 server.

    From what I have read, State 16 indicate some kind of internal error, but no idea what went wrong and how ot fix this ...

    Anyone has similar issues?

    THANKS!!

  • March 25, 2009 at 3:01 pm

    #966314

    State 16 is actually "User doesn't have permission to target database".

    From what I read, you restored the DB. Then created Logins for the already existing USER in your user DB. Keep in mind that the SID for the USER will be different from the SID of the LOGIN you just created. You should have created the Login with the same SID.

    What you can do is to drop the user for the Database (Not SQL Server) and then add the user from the newly created login.

    -Roy

  • March 25, 2009 at 4:42 pm

    #966352

    the target DB is fresh install of 2005, only have system databases. none of the users exist on the target before the restore. I have tried drop and recreate this twice from the database and then from server level, did not work. Any other suggestions?

    Thanks

  • March 25, 2009 at 10:53 pm

    #966422

    One thing I hate about those login messages they don't tell you what database it is trying to connect to.

    Turn on a profiler trace the failed login attempt with all columns selected; you should see the database it is trying to hit. Most likely it is not going to the right database and/or server :). I know working with MOSS is pain in rear, and configuring it is a bigger pain.

    Mohit.

    [font="Arial"]---

    Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
    Microsoft FTE - SQL Server PFE

    * Some time its the search that counts, not the finding...
    * I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]

    How to ask for help .. Read Best Practices here[/url].

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

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