locked
sharepoint farm/server admins missing dbo on newly created content databases RRS feed

  • Question

  • I have a problem with moss2007 - on old content databases, the server farm/server admins on my sharepoint server show up on content databases with dbo permissions in SQL.

    However, when I add a content database so that new sites can be created in it, those accounts do NOT show up with dbo permissions on the new content database.  It does not matter if I add a content database through the central admin GUI or the stsadm command line- either way, the accounts do not have dbo permission.

    How do I fix this and does anyone know why it's happening?

     

     



    • Edited by Sara Porter Monday, February 6, 2012 7:47 PM
    Monday, February 6, 2012 7:39 PM

All replies

  • Do they appear in the db_owner database role for these databases?

    Monday, February 6, 2012 10:08 PM
  • On the old databases, if I click "security" there is a list of users, and the accounts are there, under users.  When I  check the properties on them, db_owner is selected.

    On the newer databases, if I click "security" those accounts are missing entirely from the list of users. 

    Tuesday, February 7, 2012 1:20 PM
  • On the old databases, if I click "security" there is a list of users, and the accounts are there, under users.  When I  check the properties on them, db_owner is selected.

    On the newer databases, if I click "security" those accounts are missing entirely from the list of users. 

    That's not unusual. You should check if the users are members of the db_owners database role:

    In SQL Server Management Studio:

    1. Expand one of the new databases
    2. Expand Security, Roles, Database Roles
    3. Double click the db_owner role. The Database Roles Properties window will open
    4. At the bottom of this window is a section titled "Members of this role"

    If the users are in this list, then they have dbo permissions.

    That said, are you experiencing issues with these users when they attempt to access the new databases?

    Tuesday, February 7, 2012 5:12 PM
  • Hi Jason,

    I followed the steps you posted, and the accounts are not listed under "Members of this role."

    Yes, we are experiencing issues with these accounts- they cannot deploy solutions and the solutions error out on the content databases. 

    Tuesday, February 14, 2012 4:35 PM
  • I followed the steps you posted, and the accounts are not listed under "Members of this role."

    Yes, we are experiencing issues with these accounts- they cannot deploy solutions and the solutions error out on the content databases. 

    I realize this doesn't solve the problem of why the database doesn't have the correct roles, but in the meantime you can add the necessary accounts to the db_owner role to resolve the errors you are seeing. Compare to an existing database that works and add the same users to your new content database.

    What is the current farm version (Central Administration -> Operations -> Servers in Farm)?


    Jason Warren
    Infrastructure Specialist
    Habañero Consulting Group
    www.habaneros.com/blog

    Tuesday, February 14, 2012 6:03 PM
  • Hello

    we think that we have exactly the same error. we have a sharepoint 2007 farm (patchlevel i doesn't know) and a sql server 2008 service pack 3 cluster farm. when we spend the farm-admin sa-rights the problem is fixed. but with the normal permission for the farm-admin (security admin) we lose the permission for new created content databases?

    do you have a solution for this problem right now?

    Wednesday, March 7, 2012 1:16 PM
  • Hello-
    I don't have a solution for this- I suspect the only answer is to manually add accounts to those roles in SQL- which I think MS will not officially approve since they always seem to insist on not touching SQL directly.   I haven't had a chance to check with any MS support on this. 
    • Edited by Sara Porter Thursday, March 8, 2012 6:39 PM
    Thursday, March 8, 2012 6:38 PM