Insufficient SQL database permissions for user '' Event ID 5214
I am getting the Database Error Event ID 5214, with the Source of Windows SharePoint Service 3 on my MOSS 2007 SP2 server - this system has been running for the past year fine & without this error. The general text of the error in Event Viewer is: Insufficient SQL database permissions for user '' in database 'SharePoint_Config' on SQL Server instance 'illinois'. Additional error information from SQL Server is included below. The EXECUTE permission was denied on the object 'proc_getObjectsByClass', database 'SharePoint_Config', schema 'dbo'. Notice that there IS NO USER listed. I can only find articles dealing with setting the proper user permissions etc...but nothing about this. Why would no user be listed here & where do I go to fix this? Why would this error start occurring?
October 1st, 2010 6:47pm

did get a chance to see the SQL logs at the same time and see what user get the access denied. also see the ULS logs same time if you found the user name then this will help you resolve the issue:http://technet.microsoft.com/en-us/library/cc561019(office.12).aspx hope this works thanks -wsi am at SharePoint administrator
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2010 7:09pm

Hi & thank you for responding ws, The SQL logs seem to indicate that it is the user "NT AUTHORITY\NETWORK SERVICE" which fails to login with a Reason of "Failed to open the explicitly specified database". The timing appears to be correct and there are no other login failures in the sql server log anywhere near the time of the Event Viewer error originally mentioned. I found the above article prior to posting here, however, when I follow the steps in the article mentioned - I cannot get past step 2 - On the Operations page, in the Security Configuration section, click Security accounts. There IS NOT a "Security accounts" link under Security Configuration in my Central Admin/Operations page. I am logged in as a Farm Administrator and I can only see the following options under Security Configuration: Service accounts, Information Rights Management, Antivirus, Blocked file types, Update farm administrator's group, Information management policy configuration, Manage settings for single sign-on. That said, I did find that the NT Authority\Network Service user did not have db owner for the database listed in the original error, so I followed the steps to add that role on the sql server. I am not sure if that is sufficient to resolve this or if I would need to work thru the problem of accessing the 'security accounts' to set the database account. I thought that was set under the "Default Database Server" found under Data Configuration on the Operations page.
October 1st, 2010 7:52pm

Resolution: Grant correct permissions to the database access account To resolve this issue, assign the database access account and then verify the account has correct permission in SQL Server. To assign the database access account: On the Central Administration Web site, click Security and in the General Security section click Configure Service Accounts. On the Configure Service Accounts page, in the Credential Management section, select the correct Web application pool for your Web application. In the Select an account for this component section, select the domain account that you want to associate with this Web application pool, or click Register new managed account to associate a new domain account with this application pool. Note: You can use a local account for the Web application pool only if SharePoint Foundation and SQL Server are running on the same computer. Click OK to save changes. To verify that account has correct permissions in SQL Server: Connect to the computer that runs SQL Server by using an account with SQL Server administrator permissions. In SQL Server Management Studio, in the Object Explorer navigation pane, expand the Security node, and then click the Logins node. The name of the database access account indicates that it is a SQL login. If the account exists, open the database node, open the Security node, and then click Roles. Expand the Database Roles node, right-click db_owner, and select Properties. In the Database Roles Properties dialog box, check whether the database access account is in the Members of this role list. If the account is not listed, click Add. To verify that any database issues have been resolved: In the SharePoint Management Shell, run the Windows PowerShell command Get-SPSite | Format-Table -Property ID,WebApplication,ContentDatabase to obtain a list of the sites for each Web application to list all sites in the various databases, and locate one site in each database. Browse to the site.
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2011 10:12am

rahul c is refering to SharePoint 2010 so I believe this is not what you need. In general I would start with SharePoint logs and see what you have there. As far I remember if you see that source = "Windows SharePoint Service", then this means that problem comes from one of w3wp process = service account used to host SharePoint web app. Does any of your sharepoing web apps use "Network service" as hosting account ? Please also let us know what SharePoint log is saying. ps. and don't assume nothing get changed on the SQL. My SQL admins are always saying the some to me... and on the end... the true is a little diffrent then that ;) best regards Mariusz Gorzoch Blog : http://mariusz.gorzoch.pl Twitter : http://twitter.com/MariuszGorzoch
April 22nd, 2011 2:35pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics