1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

XF 1.2 Import Error [Duplicate entry 1 for key Primary]

Discussion in 'Installation, Upgrade, and Import Support' started by RoyalRumble, Feb 14, 2014.

  1. RoyalRumble

    RoyalRumble Active Member

    Hi All,

    After a successful test import without any glitch, I've attempted to import for real.

    I upgraded to 1.2.5 and began the import.

    All was going as expected, until the import Private Message option reached 100% an then hit this error;


    Anyone any ideas?
  2. Brogan

    Brogan XenForo Moderator Staff Member

    Did you drop the tables and restore your clean backup before attempting the second import?

    Did you already have a Conversation created in the destination forum and checked retain IDs?
  3. RoyalRumble

    RoyalRumble Active Member

    Thanks Brogan, as ever, for the prompt and helpful response.

    I did, my server team ensured the forum was 'vanilla', exactly was it was (minus the upgrade) in the test import. I've just dropped all tables and currently uploading the backup. Hoping advice on here will reduce a second failure.

    I did check retain IDs, perhaps I should try without retaining? Is there any implications to that?

    [Edit] The private messages actually looked to have imported fine on the forum, after it hit 100% though I couldn't continue to actual import to any other area.
  4. Brogan

    Brogan XenForo Moderator Staff Member

    Retaining IDs is used for when you want all imported content (members, threads, etc.) to keep the same IDs as the forum which you are importing from.
    The destination forum needs to be blank for that to be possible though.
  5. RoyalRumble

    RoyalRumble Active Member

    Thanks @Brogan

    A second attempt seemed to work, up until rebilding search index when I hit the below - Any ideas?

    However, it works when I disable Enhanced Search 1.0.3
  6. Brogan

    Brogan XenForo Moderator Staff Member

    That error indicates the Elastic Search service on the server isn't running.

    You may need to double check it is all installed correctly and running.
    RoyalRumble likes this.

Share This Page