Has anyone ever seen this error and know what the cause/resolution is? I checked the KBs - no joy. This is a GP 7.5 client running on SQL 2000.
Thanks in advance,
*This post is locked for comments
Has anyone ever seen this error and know what the cause/resolution is? I checked the KBs - no joy. This is a GP 7.5 client running on SQL 2000.
Thanks in advance,
*This post is locked for comments
I just fixed it.
The customer had Mekorma, not sure that was the issue here, but I found that the checkbook had allowed duplicate check numbers. M
My guess is the system was running up against a duplicate check number somehow, because unchecking that allowed the batch to print.
I'd like to add:
I cleared the batch in SY00500 and found that the Batch Status was 100, which I've never seen before. I cleared all Activity, SY00800, SY00801, DexLocks, DexSession. Also rebuilt the PM00400 table, ran Check Links on all of PM series.
Hi Frank
I have this same issue on GP2013
did you ever figure it out?
André Arnaud de Cal... 291,784 Super User 2024 Season 2
Martin Dráb 230,476 Most Valuable Professional
nmaenpaa 101,156