I have a two server MOSS 2007 SP2 Farm; version 126.96.36.19945 (Aug 2010 Cumulative). The OS is Windows Server 2003 R2 SP2 64-bit Enterprise. I am also running Forefront for SharePoint.
The Farm is deployed in a least priviledged configuration using individual service accounts for just about everything. I also have two Shared Service Providers.
Every morning around 1:59 AM I am receiving errors like the one below (I actually receive two identical ones around the same time which I'm pretty sure has to do with having two SSPs in the environment.)
In this paticular case the stored procedure is 'proc_SecAddUser'. What I've had to do to resolve similar problems is to add the Server1$, Server2$ accounts to the SharePoint_Content and SharePoint_Admin databases, add those accounts to the WSS_Content_Application_Pools roles
for each database and then apply Grant rights to that role for the given SP.
This clears up the problem for the given stored procedure in the error but the next day, at the same time, I'll get more errors telling me there are more stored procedures that cannot be executed.
Rather than doing this every day until the errors stop, I'd like to determine what process/job is responsible for the error and why there are any processes accessing the database as '
View Complete Post