2,597
*This post is locked for comments
Hossam -
We ran into this exact problem during a recent implementation of Mekorma's MICR product. The problem was caused by a missing table ME27623 and the installation of a new feature Dictionary 3183 -Assign by Checkbook. Removing the product references from the Dynamics Set file (basically uninstalling the unnecessary feature) fixed the issue. I was able to identify the problem and solution in the follow forum thread.
We had the same thing and had to open a ticket with Microsoft. Here is the answer.
"I have seen this before when there were not enough leading zeroes in front of the payment number. Go to Cards|Financial|Checkbook, select the checkbook, EFT BANK button|Payables Options and make sure the next number has room enough to grow."
We added 3 leading zeroes to the Next EFT Payment Number (which was 4999) and now it works.
Pretty pathetic system if you ask me, but life goes on. Hope this is helpful to someone!
Not sure if we can help much with this one - the error message is a bit vague.
Can you re-create the error? Can you describe exactly when it happened? What window etc.
What version of GP? Have you processed many PM documents before...or is this the first one you tried?
Is GP installed locally with a local reports dictionary, or are you operating over Citrix / RDP?
Have you and third party software running?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (