Error code 6398 - seen after Failed configuration run

Question

I tried the guidance below in order to resolve this issue however when trying to follow the steps I got the error message "Add member failed for databaseRole 'db_securityadmin' (An exemption occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Cannot use the special principal 'dbo' (Microsoft SQL Server, Error: 15405)

The guidance I followed below:

According to the information provided by the log, the problem should be that the operating account does not have the permission of the database. Any SharePoint service account that needs to access the SQL database needs Security Administrator and DBCreator permissions on the SharePoint related database.

1. Open SQL server management studio, expand Security-Logins, right-click the account you are using, select Properties, and then click Server Roles to ensure that "dbcreator", "public", "securityadmin", and "sysadmin" are checked. Then click on User Mapping, click on the corresponding database ("WSS_Content_LGPORTAL"), and make sure that in the following Database role membership for: "WSS_Content_LGPORTAL" section, "db_owner", "db_securityadmin", and "public" are checked.

2. Then, verify that the SharePoint service account has security administrator and dbcreator permissions set for the SharePoint database.

Expand Security-Server Roles, right-click securityadmin and dbcreator respectively, and make sure the accounts belong to them.

Answer 1

It seems that the login AMY\spfarm is member of sysadmin. This means that this login maps to dbo in all databases. You cannot add dbo to a fixed database role. And it does not make much sense to do so, since dbo is almighty in the database. Just like sysadmin is on the entire server.

I don't know Sharepoint, so I don't know this instruction. Maybe there is some context missing. But what you have quoted makes little sense to me, because, as I said, if you are sysadmin, you are almighty and you don't anything more.

Answer 2

Hi Tevon,

It should because you are connected as a sysadmin, you are also the dbo of the database. You cannot add dbo as a member of any fixed role. dbo already has the permissions of db_datareader and db_datawriter.

Or you can try to change the owner of the database.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.