Violation of Primary key" or "DBMS 2627" error messages when you try to create a new fiscal year

(0) Share

Report

Posted on by Community Member

When attempting to create a new fiscal year we get the error message

5516.Error-message.jpg

When clicking on OK you get

Every time we attempt to change the fiscal period to 2016 it gets stuck in in an infinite loop and we have to use Task Manager to get out of GP.

A record gets created in SY40101 but corresponding records do not get created in SY40100.

Check links and reconcile have no impact. We have recreated the fiscal periods using the steps in KB871789 but run into an issue creating a new fiscal year.

The original fiscal years were created in GP 2013 R2 which has just recently been upgraded to GP 2015 R2.

Any help would be appreciated.

Thank you.

Kathie

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Angel Nuñez on at

Like (0)

Report

I've seen this error when duplicated records for a transaction exist on open and work tables or on open and history tables for the module in which the error occurred, mostly in SOP and POP modules.

In this case, If a record is created in SY40101 but not in SY40100, I'd look for any rows in SY40100 where YEAR1 is equal to the year been created and delete it.*

* Always use a test DB to perform data manipulating troubleshooting.

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Hi Kathie,

Have you been able to fix your issue ? I've seen this a few times when using a 3rd party tool like Rockton Toolbox for GP when trying to open FY for multiple companies at a time...

Could you check your SY40100/SY40101 tables in the DYNAMICS database to see if there are any entries related to the FY Year 2016 ?

Was this reply helpful? Yes No
Suggested answer

Darryl Bajaro on at

Like (1)

Report

Hi Kathie, I have this error too and is caused by a duplicate record created on a GP table probably due to an upgrade from a previous version. You will be able to solve this by following my detailed step by step here -> darrylbajaro.wordpress.com/.../violation-of-primary-key-constraint-pksy40100-cannot-insert-duplicate-key-in-object-dbo-sy40100-the-duplicate-key-value-is-computer-checks-dbms-2627

Let me know if indeed it helped you.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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 manually. mobdro

Was this reply helpful? Yes No
jechegoyen 50 on at

Like (0)

Report

Hi ,

I realize this is an old post and I am not sure if this will be visible to everyone. I have a client that had this same issue. They upgraded from Dynamics GP 2016 to 18.4. I followed the steps Darryl provided which is very helpful. I am curious if anyone knows if the problem will occur again next year when they try to set up the new fiscal period. In 2016 when refunds were generated through the sales module, the refunds were completed with a PMCHQ batch. Since the upgrade they are showing up as PMCHK batches.

Thank you!

Was this reply helpful? Yes No