Hi All, SharePoint 2007x64 w/SP1, SQL 2005 x64,ForeFront for SharePoint w/SP1, running on Windows Server 2003 x64 R2 w/SP2. We originall setup this server using only a couple service accounts. That was a bad idea so a few weeks ago I went over everything and setup or service accounts according to Microsofts recommendations. (http://technet.microsoft.com/en-us/library/cc263445.aspx) I've gone over the requirements a dozen times and everything is set perfect. I have two issues. 1. Randomly we have a SQL permission issue popping up, this abouts a couple times a day (some days none), the event log will fill about with anywhere from 15 to 800 of the same event. Event Type:ErrorEvent Source:Windows SharePoint Services 3Event Category:Database Event ID:5214Date:3/11/2008Time:1:28:30 PMUser:N/AComputer:TRUMANDescription:Insufficient SQL database permissions for user 'PortalPool' in database 'SharePoint_AdminContent_45f0f48e-c1b1-463c-99e3-ea6648beaf37' on SQL Server instance 'Truman'. Additional error information from SQL Server is included below. The EXECUTE permission was denied on the object 'proc_UpdateVirusInfo', database 'SharePoint_AdminContent_45f0f48e-c1b1-463c-99e3-ea6648beaf37', schema 'dbo'. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. PortolPool is our service account for the IIS Pool. 2. If I run a Profile Import manually, it runs fine. If a sechduled Porfile Import is tiggered, the following is logged. Event Type:ErrorEvent Source:Office Server SearchEvent Category:Gatherer Event ID:10027Date:3/11/2008Time:2:02:23 PMUser:N/AComputer:TRUMANDescription:Failed to update committed transaction in SQL, DocID is 2414. Context: Application 'SharedServices1', Catalog 'ProfileImport' Details:Unspecified error(0x80004005) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Thanks in advance.

We get error #1 above also. Our environment is almost identical to yours, except we began the process using the "least privileged user" recommendations from MS. The error also appears to be random because it has occurred several consecutive days, and then won't occur again for 7 or 10 days. Another interesting thing to note is that first it began with our Portal service account but is now occurring with our Teams service account. Sorry, I don't have any suggestions. I just wanted to post that you're not the only one seeing that problem. Even if someone doesn't know what the cause of the problem is, can someone explain what process is trying to take place?

'proc_UpdateVirusInfo' is a SQL stored procedureused by Forefront to update some extra columns added to the SharePoint databases to provide virus status and information. I also have this error, this is what I have done to clear it (I did this five days ago and the error hasn't reoccurred, but as mentioned in the last post, it still may appear!). The issue seems to arise becausea Web application is trying to use its application pool account to execute the stored procedure on the Central Admin content database. Because these rights have not been assigned in SQL, an access denied message is thrown back on the EXECUTE command. I did the following: 1. Go to the SQL server and start the management console 2. Find the stored procedure by expanding the Admin_Content_GUID database folder, Programmability, Stored Procedures, and finally dbo.proc_UpdateVirusInfo. 3. Right-click the stored procedure and select Properties. 4. Click Permissions and add your application pool accounts to the list. Ensure the Execute permission is granted against each account. 5. Click OK. Hopefully that will help

Hey Following is the minimal permission Required for IIS Aplication Pool Account SharePoint Site Minimum Read Permission Sharepoint Server Add to WSS_ADMIN_WPG group Database Sharepoint Content DB (Site collection database) - db_owner permission Sharepoint Config DB (Config DB of sharepoint installation) - - db_owner permission If you are interested you could read more in http://sharepointinstallation.blogspot.com/2010/12/minimal-permission-required-to-execute.html