"Violation of PRIMARY KEY constraint 'PK1003255' attempt to insert a duplicate key" error message in Receivables Management Inquiry window in Microsoft Dynamics GP

Applies to: Dynamics GP 2010

Symptoms


When you look up some customers in the the Receivables Management Inquiry window, you may receive the following error message:


Violation of PRIMARY KEY constraint 'pk1003255' attempt to insert a duplicate key.

Cause


There is a duplicate record in Receivables Management violating a primary key on the table. The same record is in Work and Open, Open and History, or Work and History tables.

Resolution


Step 1: Identify duplicate records

To identify duplicate records in the Receivables Management tables, follow one of the options below. To have us identify duplicate records for you, go to the Option 1: "Fix it for me" section. To identify duplicate records yourself, go to the Option 2: "Let me fix it myself" section.

Option #1: Fix it for me

To identify duplicate records in the Receivables Management tables automatically, click the Fix this problem button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.

Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Option #2: Let me fix it myself

Identify duplicate records in the Receivables Management tables yourself. The tables are:
  • RM10301 - RM Sales Work File
  • RM10201 - Cash Receipts Work File
  • RM20101 - RM Open File
  • RM30101 - RM History File
There is an Automated Solution available to perform this task titled "Receivables Duplicates". For more information about how to identify Receivables duplicate records, visit the Automated Solutions Page at the following link:

https://mbs.microsoft.com/customersource/support/selfsupport/automatedsolutions

Note The Automated Solution will only find and report any existing duplicate records between the tables. It will not correct the issue. You must determine which records are duplicates and then you must manually delete those records after researching which record is incorrect.

Step 2: Delete duplicate records

Once you have determined which records are duplicates, research them to determine which record is valid and manually delete the duplicated record using SQL Server Management Studio. If you want assistance deleting duplicated records, contact your Partner, Technical Support for Microsoft Dynamics at 1-8888-477-7877, or open a chargeable support case.