There was a problem with lookups.  The problem happened to some of my advanced clients, too.

Sage 100 loads multiple instances of ProvideX during its execution, Each one of the instances load numinous object files and keeps them in memory. Moral of this story is you can never allocate too much memory per user session.

Open a ProvideX console and create a SY_Sesson object. You will see 20+ file handles created. A couple pointing to the same file. I would be kind in saying half the loaded code is actually used on a regular basis.