Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

"Violation of Primary key" or "DBMS 2627" error messages when you post or print in Payables Management


View products that this article applies to.

Symptoms

When you try to post or you try to print in Payables Management in Microsoft Dynamics GP or in Microsoft Business Solutions - Great Plains,youreceive one of the following error messages:
Error message 1
Violation of Primary key
Error message 2
Error attempting to insert duplicates.
Error message 3
DBMS 2627

↑ Back to the top


Cause

These errors occur after some type of posting interruption. Typically, a transaction is written to the history table. However, the interruption occurs before the transaction is removed from the work table or from the open table. Therefore, the transaction exists in both tables and violates the primary key fields of the table.

↑ Back to the top


Resolution

To resolve the problem, locate the duplicate records and then remove the appropriate record manually. This article is designed only to assist you in locating the duplicate records. If you need assistance in removing the problem records, you may contact Microsoft Technical Support or your Partnter.

To have us identify the duplicate records for you, go to the "Fix it for me" section. To find the duplicate records yourself, go to the "Let me fix it myself" section.

Method 1: Fix it for me

To locate the duplicate records 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. The Fix It will identify the duplicate records in the Payables Management (PM) tables, however, you will still need to correct them mnaually.

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.

Method 2: Automated Solution

Use the automated solution to identify the duplicate records in the Payables Management (PM) tables.

Note Before you follow the instructions in this article, make sure that you have a complete backup copy of the database that you can restore if a problem occurs.

An Automated Solution script may be available to perform this task. For more information about how to identify duplicates in Payables Management, visit the following Microsoft Dynamics Web site: Notes
  • The Fix It and the Automated Solution will report the duplicate records.
  • You should back up your company database before proceeding. You should also verify that theinformation in the History tablesis correct and complete.
  • If the duplicate records are in history and also either the work or open tables, determine if the records in the history table are valid. If so, then remove the records from the work tables or from the open tables.
  • If the duplicate records are in both the work and open tables only, determine which record is valid and remove the other record. However, when removing the problem record, keep in mind that these tables share a distribution table which also must be modified.
  • If you require further assistance regarding this process, contact Technical Support for Microsoft Dynamics at 1-8888-477-7877 or open a chargeable support case.

↑ Back to the top


Keywords: kbfreshness2007, kbmbsgp10,, kbmbspartner, kbmbsmigrate, kbmsifixme, kbfixme, kb

↑ Back to the top

Article Info
Article ID : 852808
Revision : 1
Created on : 1/7/2017
Published on : 9/12/2011
Exists online : False
Views : 296