Microsoft Dynamics GP (Archived)

GP 2016 - Dynamics GP Error "The selected document may be damaged. Please rebuild the RM Keys File to correct it "

(1) Share

Report

Posted on by Mark101

139

A user had this error on a payment record, when they were trying to apply a payment:

Dynamics GP Error "The selected document may be damaged. Please rebuild the RM Keys File to correct it "

The standard response is to run check links. However, when we ran the check links against the open transaction table in the test environment, it actually deleted the payment (which was wrong because it had posted to bank, been reconciled and posted to GL as well)

We decided then to manually fix the RM Keys table by running the following query where xxxxxx is the document number.

INSERT INTO RM00401

SELECT DOCNUMBR,RMDTYPAL,2,BCHSOURC,TRXSORCE,CUSTNMBR,CHEKNMBR,DOCDATE,0

FROM RM20101

WHERE DOCNUMBR='xxxxxx'

AND DOCNUMBR NOT IN (select DOCNUMBR from RM00401)

This resolved the issue without deleting a valid document. I was surprised to see that running check links made the issue worse, by removing data from the RM20101 table. In older versions of GP, I was used to seeing the RM_Keys record get added back, based on the actual transaction information.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Community Member on at

Like (1)

Report

RE: GP 2016 - Dynamics GP Error "The selected document may be damaged. Please rebuild the RM Keys File to correct it "

Since ISAM file systems had no ability to support referential integrity, the Dynamics development team had to create their own routines to analyze and maintain data integrity Walgreens Listens.

Was this reply helpful? Yes No
Mark101 139 on at

Like (0)

Report

RE: GP 2016 - Dynamics GP Error "The selected document may be damaged. Please rebuild the RM Keys File to correct it "

I found this very old link from 8 years ago:

microsoft.public.greatplains.narkive.com/.../how-to-rebuild-rm-keys

I just ran this procedure on the TWO company data in GP 2016 and it worked. So I am at a loss to understand why it did not work for the other situation. However, at this point, I am going to chalk it up to some other data issue that caused check links to decide to remove the payment record from the open table, rather than re-create the missing RM_Keys record.

Was this reply helpful? Yes No
Mick Egan 3,561 on at

Like (0)

Report

RE: GP 2016 - Dynamics GP Error "The selected document may be damaged. Please rebuild the RM Keys File to correct it "

I have always rebuilt the RM00401 manually like your code, sometimes we find the RM10101 is missing as well, and need to get the detail from the GL20000 table.

Mick

Was this reply helpful? Yes No
Mark101 139 on at

Like (0)

Report

RE: GP 2016 - Dynamics GP Error "The selected document may be damaged. Please rebuild the RM Keys File to correct it "

Thanks Mariano. In previous versions, I was able to re-build the RM00401 table by clearing the data in that table and running check links (GP version 9, 10, 2010?)-- so somewhere along the line it changed for this particular issue. I have had better luck, in that most of the check links I have run have had a more positive outcome. However, backups and running in a test environment before running it in live is a good practice.

The link is very helpful, but I'd like to know if anyone else has experienced this issue: Missing RM_Keys record on a payment in the open table.

Was this reply helpful? Yes No
Verified answer

Mariano Gomez 26,225 on at

Like (3)

Report

RE: GP 2016 - Dynamics GP Error "The selected document may be damaged. Please rebuild the RM Keys File to correct it "

Check Links is always been a destructive process. It is meant to catch inconsistencies and remove those inconsistencies. Very seldom does it really re-add a record. Take a look at my article, How Does Check Links Work? for more information.

Was this reply helpful? Yes No