Tuesday, April 03, 2007

SharePoint V2: ERROR: CREATE DATABASE permission denied in database 'master'. (Error code: 262).

Description:

From SharePoint Central Administration, attempting to create a new configuration database results in an error: "Error CREATE DATABASE permission denied in database 'master'. (Error code: 262)."




Solution:

* Start > Programs > Administrative Tools > IIS Manager > SharePoint Central Administration Web Site Properties > Home Directory Tab: Note the Application Pool Name (e.g. StsAdminAppPool).

* Start > Programs > Administrative Tools > IIS Manager > StsAdminAppPool Properties > Identity Tab: Set the user name and password to be the same as the database service account.

* Start > Run > IISRESET

4 comments:

  1. Anonymous6:47 PM EDT

    YESSSSSSSSSSSSSSSS - YOU RULE!

    ReplyDelete
  2. Anonymous7:53 PM EDT

    RIGHT ON!!! THANKS!!!

    ReplyDelete
  3. Anonymous8:05 AM EST

    We tried the same in WSS2 environment. But unfortunately it didn't work. Basically, we had a content database - CD1 being used for Web APP1. Recently, we removed the CD1 and used CD2 in its place for Web App1.

    But, now we want to attach the Content DB - CD1 to a new web app created - WEb App2.

    But, when we tried to "Extent & Create a content DB" & attach the content db - CD1 .. we are getting this above mentioned : "CREATe db PERMISSION denied in database 'MASTER' (Error Code: 262)

    Any urgent help on this is greatly appreciated.

    ReplyDelete
  4. If you are getting the "CREATe db PERMISSION denied in database 'MASTER' (Error Code: 262)" check this:

    - Make sure there is a SQL Server login associated with the

    - Make sure that service account has is at least in dbcreator and securityadmin SQL Server roles. Depending on your security requirements, you can elevate the role even higher to one of the other roles.

    - If you still have issues with the MASTER, manually map that service accounts SQL login to have excplicit permissions on the MASTER.

    Some times you have to elevate the permissions beyond what best practices say for security(e.g. elevate to sysadmin, serveradmin roles) to get something working, then gradually scale it back aftwards to identify exactly where it is falling apart.

    ReplyDelete