Stored Procedure Priming and Identity Reseeding

• Question

• 

  

  0

  Sign in to vote

  Hello,
  I see that this question has been asked before, but has not been answered.  There are two scheduled jobs on my CRM 4 SQL Server Agent that are failing over and over again, and I have hit a wall attempting to fix them.  The first is "MSCRM Stored Procedure Priming", which fails with the following error:
  
  
  Date        9/28/2009 2:50:00 PM
  Log        Job History (MSCRM Stored Procedure Priming)
  
  Step ID        1
  Server        CAMDATA
  Job Name        MSCRM Stored Procedure Priming
  Step Name        Execute Priming Stored Procedure
  Duration        00:00:01
  Sql Severity        16
  Sql Message ID        201
  Operator Emailed       
  Operator Net sent       
  Operator Paged       
  Retries Attempted        0
  
  Message
  Executed as user: NT AUTHORITY\SYSTEM. Procedure or function 'p_CascadeCollect' expects parameter '@old_owner', which was not supplied. [SQLSTATE 42000] (Error 201).  The step failed.
  
  
  The second is "MSCRM Identity Reseeding", which fails with the following error:
  
  Date        9/26/2009 12:00:00 AM
  Log        Job History (MSCRM Identity Reseeding)
  
  Step ID        1
  Server        CAMDATA
  Job Name        MSCRM Identity Reseeding
  Step Name        Execute Reseeding Stored Procedure
  Duration        00:00:00
  Sql Severity        16
  Sql Message ID        2812
  Operator Emailed       
  Operator Net sent       
  Operator Paged       
  Retries Attempted        0
  
  Message
  Executed as user: NT AUTHORITY\SYSTEM. Could not find stored procedure 'p_Reseed'. [SQLSTATE 42000] (Error 2812).  The step failed.
  
  
  Looking at these errors, it seems like these jobs are either obsolete, or something has become horrible mangled with my CRM deployment.  Has anyone else experienced these issues?  Is anyone else running these jobs successfully?
  
  Thanks,
  Sean McGinnis

  Monday, September 28, 2009 7:02 PM