Question

Photo of Frank Grand

0

Calculate Person Duplicates Job Failing?

4

The calculate person duplicates job keeps failing....here is the exception I get.  Can anyone help me shed any light on this?

exception.JPG

  • Photo of Mike Peterson

    0

    OK, I think I figured it out. If some of the person records have multiple home phone numbers and/or multiple cell phone numbers, this could happen. 

    ted decker phones.png

    The Rock UI only lets you have one of each type of phonenumber, so those duplicates must have gotten in some other way.  I've created https://github.com/SparkDevNetwork/Rock/issues/694 to address this.

  • Photo of Mike Peterson

    0

    Has it done this more than once? 

  • Photo of Frank Grand

    0

    It's failed every day since 9/14.  Job looks like it's scheduled to run at 3am each day.

  • Photo of Frank Grand

    0

    Mike, still getting this almost everyday.....anything to be worried about?

    Capture1.JPG

    • Mike Peterson

      Mike Peterson

      oops, sorry I didn't back to you when you responded a month ago! I'm having trouble reproducing this. Would you be able to run this in Sql Server Management Studio? "EXEC [dbo].[spCrm_PersonDuplicateFinder]". Then let me know what the exception looks like. Hopefully it'll tell you what line number.

      • Frank Grand

        Frank Grand

        Here is what it says:
        Msg 2601, Level 14, State 1, Procedure spCrm_PersonDuplicateFinder, Line 454
        Cannot insert duplicate key row in object 'dbo.PersonDuplicate' with unique index 'IX_PersonAliasId_DuplicatePersonAliasId'. The duplicate key value is (47973, 47972).
        The statement has been terminated.
        Msg 2601, Level 14, State 1, Procedure spCrm_PersonDuplicateFinder, Line 454
        Cannot insert duplicate key row in object 'dbo.PersonDuplicate' with unique index 'IX_PersonAliasId_DuplicatePersonAliasId'. The duplicate key value is (45518, 45513).
        The statement has been terminated.

        • Frank Grand

          Frank Grand

          I don't think so, only because we are using SQL 2014. Would that fix have been including with future versions?