This turned out to be a programming issue / bug with the Restart logic of AR Sales Journal Update on v2013 / 5.00. Haven't checked if more recent versions have this but I suspect so.
It was looking at the InvoiceHistoryHeaderSeqNo variable to figure out if the DocSequenceNo field in GL_DailyPosting needed to be updated. Well the variable was unexpectedly blank but it still tried to run routines called UpdateDailySeq() and UpdateDrilldownSeq). The WHOLE problem is this particular block doesn't 1st check to see if it's in the middle of a restart because if it had it would conditionally decide to bypass this block, ergo no error.
(Also when you try do to a ProvideX SELECT stmt on a file channel that is not open, you get an Error 84, a complete red herring in this case)
I clicked on Info / Debug and at prompt typed GOTO xxxx (a line number) a few times, manually ran a few lines then got it to where it returned back to the variable test. Then PRINT 'POP';RUN from there. This resumed execution of the Update and completed it. Nobody here should expect to know that.
------------------------------
Alnoor Cassim
Email:
alnoor@asifocus.comPh: 949-689-9887
Orange County, CA
------------------------------
Original Message:
Sent: 11-11-2021 01:35
From: Shannon Sadowsky
Subject: Anyone seen this error - Error 84 No DICTIONARY ex
Thank you @David Speck II for the reply. I tried rebuilding the AR Keys and Sorts. I reinitialized AR_InvoiceHeader, AR_InvoiceDetail, and AR_InvoiceRestart. Nothing I tried corrected the issue. Called Sage and as figured, their answer was that they couldn't help me. So... I used my "phone a friend" option. @Alnoor Cassim saved the day and will post the resolution that worked for this client and may help others too, if this happens to them.
------------------------------
Shannon Sadowsky
RKL eSolutions, LLC
------------------------------
Original Message:
Sent: 11-09-2021 11:07
From: David Speck II
Subject: Anyone seen this error - Error 84 No DICTIONARY ex
Shannon, click Info to see if you can see which table might be involved. If you can try using Rebuild Key Files for the file in question. Something else you could try is to use the following KB on the AR module. Wouldn't hurt to make sure you have a good back up first to be safe.
https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=23940
------------------------------
David Speck II
Tennessee Software Solutions
Original Message:
Sent: 11-08-2021 13:01
From: Wayne Schulz
Subject: Anyone seen this error - Error 84 No DICTIONARY ex
Sorry I don't find any other notes on my end
The only suggestion I made ( which I can find ) was for the customer to turn off PEP and they said it didn't work
------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
Original Message:
Sent: 11-08-2021 12:42
From: Shannon Sadowsky
Subject: Anyone seen this error - Error 84 No DICTIONARY ex
Hi @Wayne Schulz - We have a client with a similar error but in AR for v2013. Do you recall what you needed to do to correct this as I don't see a resolution listed?
------------------------------
Shannon Sadowsky
RKL eSolutions, LLC
Original Message:
Sent: 05-29-2015 04:24
From: Wayne Schulz
Subject: Anyone seen this error - Error 84 No DICTIONARY ex
I'm not sure - the user sent me a screen shot then wasn't around when I called