Microsoft KB Archive Search

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.

  1. Home
  2. "GPS Error: 54", " SQL Error 2601", or "ODBC Error: 2300" when running FA to GL Posting in Fixed Assets after upgrading to Microsoft Dynamics GP 2013

"GPS Error: 54", " SQL Error 2601", or "ODBC Error: 2300" when running FA to GL Posting in Fixed Assets after upgrading to Microsoft Dynamics GP 2013

View products that this article applies to.

Symptoms

After migrating to Microsoft Dynamics GP 2013, you receive all of the following error messages when running GL Posting:

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 (120151(.

ODBC Error: 23000


↑ Back to the top

Cause

This issue has not be able to be recreated in-house, and therefore no cause has been identified to date. However, all customers experiencing this have just upgraded to Microsoft Dynamics GP 2013. The problem itself deals with the new functionality added to the FA00905 where, when any data is brought into this table by clicking Process in the GL Posting window, the data should have the GLINTBTCHNUM field in the FA00905 table populated with the FATRX Batch ID that was showing in the GL Posting window prior to clicking Process. For this issue, the GLINTBTCHNUM field in the FA00905 is blank for the transactions added into this table.

↑ Back to the top

Resolution

To resolve, you need to remove the corrupted data from the FA00905 table where the GLINTBTCHNUM is blank. If you test the usage of this table in Microsoft Dynamics GP 2013, you will see the GLINTBTCHNUM field for the records in the FA00905 table is populated with the Batch ID from the GL Posting window at the time Process was clicked.


1. To view the corrupted records, run the following select statement against the company database in SQL Server Management Studio:

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

2. If the records returned in step 2 are all damaged records and need to be removed, run the following delete statement against the company database in SQL Server Management Studio:

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

3. Now re-run the GL Posting process and the issue should be resolved.




↑ Back to the top

Keywords: kbmbspartner, kbmbsmigrate, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2930489
Revision : 1
Created on : 1/7/2017
Published on : 6/16/2014
Exists online : False
Views : 213