Sage 100

Error resolution (for anyone who runs into this message): Rebuilt the PL_JournalPDFLog.M4T using *UFAR which found a couple errors and resolved the issue. Error 108 PL_CommonUtility.PVC Line 2455 WritePDFLOG There were no direct KB entries but I followed one that mentioned the PL_CommonUtility.PVC and that did the trick with the *UFAR. As an aside, how embarrassing is it to still struggle with old DOS based utilities.

Any idea on what caused the issue? It almost reads like you did a test conversion from v4.5(?) to a later release, then went live by copying the latest v4.5 log file over to the go live version which has new key length for the log file instead of using the @JimWoodhead utility to copy the additional records to the new version file.

No this was someone on 2013 who I installed the latest PU for. Unsure if it's related or simply coincidental. Suddenly today they were unable to update a sales journal and received the message noted.

FYI - all the low 100 errors are related to key corruption within the data file itself. Usually, the data records are OK and can be read individually and written to a new copy of the data file with the freshly hashed key value and this corrects the problem. This is what *UFAR and Rebuild Key File utilities do. Not sure what exactly causes the original corruption, but this corrects the symptom. Luckily, it doesn't happen all that often....