web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / "GPS Error: 54&qu...
Microsoft Dynamics GP (Archived)

"GPS Error: 54", " SQL Error 2601", when running FA to GL Posting in Fixed Assets

(0) ShareShare
ReportReport
Posted on by Linda Brock 18

Hi,

My client is unable to post her fixed assets. She gets the following error:

+++++++++++++++++++++++++++++++++++++++++

 An error occurred executing the SQL Statements.
GPS Error: 54
SQL Error: 2601 [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot insert duplicate key row in object ‘dbo.FA00905’ with unique index ‘AK2FA00905’. The duplicate key value is (9984.)

++++++++++++++++++++++++++++++++++++++++++++++

We found the following post

https://support.microsoft.com/en-us/help/2930489/gps-error-54-sql-error-2601-or-odbc-error-2300-when-running-fa-to-gl-p

However, when we run

select * from FA00905 where GLINTBTCHNUM = ''
/*two single apostrophes denote a blank entry*/

The FA00905 table does not have any “Blank”  entries for the GLINTBTCHNUM column.

Also, this client is on GP2016R2

Other suggestions?

Thanks,

Linda

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    MG-16101311-0 Profile Picture
    MG-16101311-0 26,225 on at

    That support article is totally messed up :)

    Index AK2FA00905 actually seems to have the FINANCIALINDX column as the main and only column for that key, which is unique. The error tells you which value renders the key duplicate, so the statement is more like this:

    SELECT * FROM FA00905 WHERE FINANCIALINDX = 9984;


    If you run this statement, I should return a record. This record needs to be removed from the table, before you can post.

  • Verified answer
    Linda Brock Profile Picture
    Linda Brock 18 on at

    Turns out that when we ran this:

    SELECT * FROM FA00905 WHERE FINANCIALINDX IN (SELECT FINANCIALINDX FROM FA00902 WHERE GLINTBTCHNUM = '')

     

    A bunch of rows were returned - with FATRX numbers not in synch with the next number.

     

    So, we ran this:

     

    DELETE FA00905 WHERE FINANCIALINDX IN (SELECT FINANCIALINDX FROM FA00902 WHERE GLINTBTCHNUM = ''

     

     

    Which fixed it and the client was able to run the GL Posting routine.

    However, the exact same error recurred the next time the client ran GL Posting in this company.

    The delete statement above fixed it again.

    I suppose if it happens a third time, we'll delve into it further. :-(

     

  • Victoria Yudin Profile Picture
    Victoria Yudin 22,769 on at

    Thank you Linda, this just helped me with a similar error! 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans