This Error Message Article explains the BACKTRACK error message “[BT App Name] [Table Name]: Table has non-unique records. These columns don’t currently have unique values.” and details how to fix the underlying problem that caused it to appear.
BACKTRACK has encountered records with duplicate key field values. This has been seen with the GROUP, RELATION, and ITEM tables. In some cases, BACKTRACK will allow the user to complete the transaction but send the notice anyways.
The duplicates with the GROUP table are common with migrations from v6 or before to v2012 or later. For some reason, the migration process ends with duplicate Security Groups.
The same error message appeared with the “RELATION” table in a couple of situations:
- During re-import of transactions into the Transactions table, the specific reason was never determined
- At the start of an import into the Item table using an import file with blank records (extra blank line at the end of the file)
This was also the result of an migrated BACKTRACK system. The duplicates had to be removed using SQL.
In this situation, it is most likely that you will need assistant from IT. You need to go into the database, determine which records are duplicate and remove them.
Note: please exercise extreme caution when working with the database tool. In addition to knowing how to use the tool (SQL Management Studio), you need to understand the table relationship. If you are unsure or need assistant, please contact EBI Support.
Issue found running: BACKTRACK v2012 (from BT6), client running on Windows XP workstation, Server on Windows Server 2008.