This is actually why I started blogging.

Ran across this issue deploying the Feb 2012 CU update for a SharePoint 2010 customer;

[OWSTIMER] [SPUpgradeSession] [ERROR] [6/12/2013 2:46:34 PM]: Exception: Cannot drop the procedure ‘MSP_WEB_SR_DeleteUserData’, because it does not exist or you do not have permission.
Cannot drop the procedure ‘MSP_SECURITY_CREATE_PROJECT_OWNER’, because it does not exist or you do not have permission.
Cannot drop the procedure ‘MSP_DELETE_PROJECT_LOOKUP_TABLES’, because it does not exist or you do not have permission.

… (continues for a few hundred other lines)

 

Unfortunately a quick Google search came up with only the following; http://dzeee.net/sharepoint/post/2011/03/23/MOSS-2007-Feb-CU-2011-Installation-issues.aspx

Unfortunate because the proposed solution is to disable and recreate the specified service applications (Search in their case), now as I didn’t want to have to practically reinstall SharePoint this wasn’t going to happen.

 

Better Solution

Fortunately the the source above was onto something, the solution was simply to stop all related SharePoint Windows Services (not SharePoint services), so in my case stop:

  • Project Events Service
  • Project Queue Service
  • SharePoint Administration
  • SharePoint Timer
  • SharePoint Tracing
  • SharePoint User Code Host
  • SharePoint Server Search

Then run PSCONFIG from the command line:

psconfig.exe -cmd upgrade -inplace b2b -wait –force

 

PSConfig automatically starts any needed services, then at the end restarts the others with only the exception of the Project services which I had to start manually.