The error:
“Cannot add <user> to the SharePoint_Shell_Access role of the database SharePoint_Config_<Guid>. A possible cause of this error is that the account name was already added to the database as a login using a different user name than the account name.”
The DB_Owner Role is replaced by the SP_DataAccessRole in SharePoint 2013. This role is detailed here:
https://technet.microsoft.com/EN-US/library/cc678863.aspx#Section4
_The SP_DATA_ACCESS role is the default role for database access and should be used for all object model level access to databases. Add the application pool account to this role during upgrade or new deployments.
Note:
The SP_DATA_ACCESS role replaces the db_owner role in SharePoint 2013.
The SP_DATA_ACCESS role will have the following permissions:
Grant EXECUTE or SELECT on all SharePoint stored procedures and functions
Grant SELECT on all SharePoint tables
Grant EXECUTE on User-defined type where schema is dbo
Grant INSERT on AllUserDataJunctions table
Grant UPDATE on Sites view
Grant UPDATE on UserData view
Grant UPDATE on AllUserData table
Grant INSERT and DELETE on NameValuePair tables
Grant create table permission
_
This is the role given to the Install account by the farm account during the user profile sync service app creation instead of the db_owner role. This is because the Add-SPShellAdmin in SP 2013 starts by looking for the SP_Data_Access role on the database and if this role is found it is used. if not it uses the db_owner role.
The SP_Data_Access role does not give the install or setup account enough permissions to run an add-spshelladmin for other service accounts against the upsa databases (profile and social dbs). setting the setup account as db_owner on those dbs fixes this. Giving the setup account sysadmin rights fixes it too.
So I guess a new fix is on the way Brian :-)
Comments: ** Comment from web user: brianlala **
“Cannot add <user> to the SharePoint_Shell_Access role of the database SharePoint_Config_<Guid>. A possible cause of this error is that the account name was already added to the database as a login using a different user name than the account name.”
The DB_Owner Role is replaced by the SP_DataAccessRole in SharePoint 2013. This role is detailed here:
https://technet.microsoft.com/EN-US/library/cc678863.aspx#Section4
_The SP_DATA_ACCESS role is the default role for database access and should be used for all object model level access to databases. Add the application pool account to this role during upgrade or new deployments.
Note:
The SP_DATA_ACCESS role replaces the db_owner role in SharePoint 2013.
The SP_DATA_ACCESS role will have the following permissions:
Grant EXECUTE or SELECT on all SharePoint stored procedures and functions
Grant SELECT on all SharePoint tables
Grant EXECUTE on User-defined type where schema is dbo
Grant INSERT on AllUserDataJunctions table
Grant UPDATE on Sites view
Grant UPDATE on UserData view
Grant UPDATE on AllUserData table
Grant INSERT and DELETE on NameValuePair tables
Grant create table permission
_
This is the role given to the Install account by the farm account during the user profile sync service app creation instead of the db_owner role. This is because the Add-SPShellAdmin in SP 2013 starts by looking for the SP_Data_Access role on the database and if this role is found it is used. if not it uses the db_owner role.
The SP_Data_Access role does not give the install or setup account enough permissions to run an add-spshelladmin for other service accounts against the upsa databases (profile and social dbs). setting the setup account as db_owner on those dbs fixes this. Giving the setup account sysadmin rights fixes it too.
So I guess a new fix is on the way Brian :-)
Comments: ** Comment from web user: brianlala **
Hmm I've not run into this myself, probably because I always insist that the setup account has sysadmin on the SQL instance from the get-go. Yet another reason why I will continue to insist on this I guess :)
Brian