Just as the subject says, I have run in to an instance where a sage 100 install is emailing the wrong contents in pdf's to customers. Previously fixed, but the issue keeps coming back. 
So far, I have had several support tickets about the issue. Thought it was resolved for good last time.

At first, the problem was resolved by going in to PL_AdvancedOptions_UI and making sure that per company file, that the "Use lockfile" was turned back on and removing and reinstalling the pdf converter with that checked. 

The problem went away for a long while. 

Recently the problem has cropped up at random again along with users at random getting errors regarding lock files. Usually the lockfile error issue clears it self up if the user try's again.

Things to note:
1. Already went back in to PL_AdvancedOptions_UI and made sure that some how, the "Use lockfile" was not unchecked. System wide. 
2. Double checked permissions as per another past sage KB article that phone support lead me to, on registry entries for the lockfiles. 
3. The attached pdf sent to the customer is named correctly, just has the wrong contents from a different invoice. 
4. Happens totally at random with no relation to company file. 
5. This is an RDS web app deployment of sage to 30 or so users spanning multiple states, not company intranet setup, so internet connection speed is not a factor since users are interacting with a remote desktop view. 
6. Has been running seamlessly for months, minus a few typical RDS deployment issues that crop up from time to time.
7. There is a total of 18 separate active company code's in this deployment.

My question is, has any one had this issue keep croping back up?
I suspect that going back in to each company file in sage and running the PL_AdvancedOptions_UI utility again to uncheck "use lockfile", uninstall the pdf converter, recheck "use lockfile", and reinstall the pdf converter, will clear up the issue yet again
Desperately searching for a final resolution to this issue. 
I have at length tried to search and find a relevant KB article to solve this once and for all.