Answers.Body: <p>Thanks to Jamie McClelland, there is a patch available to make this more user-friendly. At some point hopefully it will be merged into core.</p>
  
  <ul>
  <li>JIRA: <a href="https://issues.civicrm.org/jira/browse/CRM-19664" rel="nofollow noreferrer">https://issues.civicrm.org/jira/browse/CRM-19664</a></li>
  <li>PR: <a href="https://github.com/civicrm/civicrm-core/pull/9410" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/9410</a></li>
  </ul>
  
  <p>With this patch applied, instead of a fatal error, the import will continue and the problem rows will be pulled out in an error file at the end.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-04T16:12:27.123Z
Answers.LastActivityDate: 2017-05-04T16:12:27.123Z
Answers.UserDisplayName: Laryn
Body: <p>I've had a few separate imports crash with a fatal error in the last month:</p>
  
  <blockquote>
    <p>Sorry but we are not able to provide this at the moment.
    DB Error: already exists</p>
    
    <p>Fatal error: Uncaught CRM_Core_Exception: [0: Transaction integrity error: Expected to find active frame thrown in /home/user/public_html/sites/all/modules/civicrm/Civi/Core/Transaction/Manager.php on line 107</p>
  </blockquote>
  
  <p>In my case it seems to have something to do with external IDs that already exist in the database and are also in the import file. How can I avoid having imports fatally die in the middle of things?</p>
  
Tags: <import><duplicate-contacts><external-id>
Title: How can I avoid my import crashing with a Fatal Error due to an existing external ID?
ThreadText: # How can I avoid my import crashing with a Fatal Error due to an existing external ID?
  
  (Asked by: username_0 on 2017-05-04)
  
  I've had a few separate imports crash with a fatal error in the last month:
  
  > Sorry but we are not able to provide this at the moment.
  > DB Error: already exists
  >
  > Fatal error: Uncaught CRM\_Core\_Exception: [0: Transaction integrity error: Expected to find active frame thrown in /home/user/public\_html/sites/all/modules/civicrm/Civi/Core/Transaction/Manager.php on line 107
  
  In my case it seems to have something to do with external IDs that already exist in the database and are also in the import file. How can I avoid having imports fatally die in the middle of things?
  
  **Tags:** import, duplicate-contacts, external-id
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2017-05-04. Score: 2 | Accepted answer
  
  Thanks to Jamie McClelland, there is a patch available to make this more user-friendly. At some point hopefully it will be merged into core.
  
  * JIRA: <https://issues.civicrm.org/jira/browse/CRM-19664>
  * PR: <https://github.com/civicrm/civicrm-core/pull/9410>
  
  With this patch applied, instead of a fatal error, the import will continue and the problem rows will be pulled out in an error file at the end.
  
  
  ---
  
  