We're seeing this for a customer on Premium 2020.1.  Did you find a cause / solution?

We did not find the cause of this. If I remember correct the solution was to close out the application service and restart, making sure all the pvxwin32 programs were closed. 

Thanks Tim.

So it was a one-time thing for you, and it hasn't come back after resetting the service?

Do you have any enhancements?  Customizations in SQL (scripts / triggers...)?

Our customer thinks it might be their website integration (from a very skilled member of the Sage 100 community), and I'm wondering if it's the SQL scripts I use to change UDF flags for a couple custom report processes.

Yes, it was a one-time issue for us, and it has not come back. We do run Sage 100 as an application rather than a windows service .We do have enhancements with  scads of scripts and some SQL triggers. For our web integration we do use a module from ROI rather than BOI/Web services as we had done that in the past.