Unhandled database exception: A get/change operation on table 'PM_Key_MSTR' could not find a record.

(0) Share

Report

Posted on by Rai

585

Hi,

Can someone help me in the issue we encounter. We finish activating the Analytical Accounting and Grant Management for GP2010. But in the Payable Transaction Entry we encounter an error when we click the previous button "Unhandled database exception:

A get/change operation on table 'PM_Key_MSTR' could not find a record.

EXCEPTION_CLASS_DB

DB_ERR_MISSING"

Regards,

Rai

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Sureshn07 702 on at

Like (0)

Report

here you go

support.microsoft.com/.../852208

Was this reply helpful? Yes No
kj_henkelman on at

Like (0)

Report

I ran into this exact same issue in GP 2016, but AA was not involved. I thought I'd post here what we found in our case, since there aren't any answers.

Scribe was running, and had errored during Payables transaction entry. It had already completed the "get next number" step, but errored on a later step and for some reason didn't roll back (even though it was set to do so). So it had locked up the next number - but not the table, because I was able to update the next voucher number in the setup in GP. I'm not sure what was locked up. But as soon as I fixed the issue in the Scribe integration and ran the records successfully into Payables transaction, we no longer had this issue.

Was this reply helpful? Yes No
Anwar Aziz 15 on at

Like (0)

Report

Hi KJ, we are running into the same error with one of our company's. Our AP department is having trouble posting and deleting batches with the error coming up. Can you please describe what the Scribe integration did and how to run this is GP so I can resolve. Thanks

Was this reply helpful? Yes No
kj_henkelman on at

Like (0)

Report

The Scribe integration was creating PM transactions, and including an insert/update of a translation table in SQL as one of the steps. It was erroring on this insert/update step - so it would get the next transaction number in GP, but then never actually get to the step of entering the transaction. To resolve, I used SKIPSTEP() in the flow control formula, so that it would skip the step that was erroring. I ran it the integration (manually from the dts file), and it ran without error. Since Scribe was able to complete the process, this apparently freed up whatever process or table had been stuck, because the GP error didn't occur again.

Was this reply helpful? Yes No
Anwar Aziz 15 on at

Like (0)

Report

Hi KJ,

I used the below article to trouble shoot this issues in our testing environment after restoring the database. After running the SQL scripts no errors or transactions appeared. I then completed for the purchasing module check links and was able to access and post the batch without any errors. Check Links had the below message. I have a question about running checklinks in production. Should I have all users log out of the system or just the users for the company i'm updating checklinks with.

https://support.microsoft.com/en-us/help/852208/error-message-when-you-print-checks-in-payables-management-in-microsof

Best Regards

Was this reply helpful? Yes No
kj_henkelman on at

Like (0)

Report

If you're just running against the PM module, you don't have to get people out of other companies because you're only working with tables for that company. I tend to be extra cautious and have everyone log out of GP anyway (if it's not too much of a hassle). In the least, though, if you do have people log out of the company, lock it down using the Administration > Utilities > Take Company Offline. That way you won't have people logging into that company while you're working on it.

Was this reply helpful? Yes No